[Info-vax] hung program location

[Stephen Hoffman]

On 2013-02-18 14:15:28 +0000, Tom Adams said:

> I can see the PC and SP where a program is hung using SHOW PROC/CONT.
> 
> How can I relate that to a link map to figure out where the process is
> hung in the program that it is running?
> 
> The process is running an installed shared image
> 
> This is VMS 7.3-2 on an alpha


The sequence is generally the same as is used to troubleshoot the 
source of an ACCVIO: <http://labs.hoffmanlabs.com/node/800>, though 
you're looking at "live" memory here, and not at the debugger or the 
process dump carcass.

Depending on how the process is wedged, consider configuring the 
application image and potentially the shareable image for debugging or 
for integrated logging, force a process dump, and then use the debugger 
on the carcass.  Some details on debugging detached processes are 
available here <http://labs.hoffmanlabs.com/node/803>

Addresses in P1, S0 or S2 space are usually a result of a system call, 
and figuring out what call and what application code triggered the call 
involves walking the call stack.  That's slightly more involved, and I 
don't have an article posted on that.  It's usually easier to integrate 
and use the debugger for those cases — as described above — and let 
that walk the call stack for you.


-- 
Pure Personal Opinion | HoffmanLabs LLC