Native Inspect Manual (H06.04+)

Syntax of Native Inspect Commands
Native Inspect Manual—528122-005
4-17
catch command
Example
To display the current frame:
catch command
Sets a logical breakpoint on a specified event (a catch event). A catch event is similar
to a breakpoint except that a catch event is associated with a logical event rather than
a code location.
Catch events are treated as breakpoints and each catch event has an associated
breakpoint number. You can use all the breakpoint-related commands to manage catch
events. This includes the commands command, condition command, delete command,
enable command, disable command, and info command with the breakpoints option.
event
is the event on which the process will be held:
•
STOP holds the process on a STOP event.
•
ABEND holds the process on an ABEND event.
To display a list of current catch events, use the info command with the breakpoints
option.
Managing a Stopping Process (STOP and ABEND Events)
When a process triggers a STOP or ABEND event, the process is in a stopping state.
You can examine a process that is in a stopping state, but the process cannot execute
any further. Execution control commands are disabled when a process is suspended at
a STOP or ABEND event. You can use the save command to create a snapshot of a
stopping process.
You can switch a stopping process to another debugger by using the switch command.
The process is eventually given back to the original instance of Native Inspect, and the
process will still be in the stopping state.
After you examine a stopping process, you must use the continue, detach, or kill
command to disassociate the process from Native Inspect and allow the process to
terminate.
(eInspect 4,770): bt
#0 pcbDataStructs_initialize () at \SIERRA.$YOSE1.SYMBAT1.SCXXTST:362
#1 0x700016a0:0 in main (argc=1, argv=0x8003010)
at \SIERRA.$YOSE1.SYMBAT1.SCXXTST:217
#2 0x700011f0:0 in _MAIN () at \SPEEDY.$RLSE.T8432H01.CPLMAINC:68
catch event