Native Inspect Manual (H06.13+, J06.03+)

Num Type Disp Enb Glb Address What
2 mem access brk keep y n globStr.f2 -c
bt (tn) Command
Prints a backtrace of all stack frames. Frame numbers are preceded by a number sign, (#).
Alias: tn.
{bt|tn} [count]
Where:
count
An integer that displays a backtrace of the innermost count frames. If you specify a negative
count, then a backtrace of the outermost -count frames is displayed.
Consideration for Debugging TNS Processes
Although Native Inspect does not debug TNS processes, the bt command displays a TNS stack
trace.
Example
To display the current frame:
(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 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 event
Where:
event
The event on which the process will be held. Supported events are:
• STOP – Holds the process on a stop event.
• ABEND – Holds the process on an abend event.
• LOAD [dllname] – Holds the process on the loading of a DLL. If you specify dllname,
the process is held when the specified DLL is loaded. If you omit dllname, the process is
held when any DLL is loaded.
• UNLOAD [dllname] – Holds the process on the unloading of a DLL. If you specify
dllname, the process is held when the specified DLL is unloaded. If you omit dllname,
the process is held when any DLL is unloaded.
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 following:
• commands (see commands Command (page 70)).
• condition (see condition Command (page 71)).
• delete (see delete Command (page 73)).
• enable (see enable Command (page 78)).
bt (tn) Command 69