System Debug Reference Manual (32650-90888)

250 Chapter6
System Debug Command Specifications M-X
PURGEDUMP
(switch marker frame)
b) SP=40223bc0 RP=a.00597274 switch_to_cm+$8c4
c) SP=402239d0 RP=a.007499b8 tm_cms_type_mgr+$8bc
d) SP=40223668 RP=a.0072ee44 FREAD+$3c8
e) SP=40221780 RP=a.006ac858 readcmd+$1dc
f) SP=40221560 RP=a.006abcc8 ?readcmd+$8
export stub: 74.00006274 ci_cmd_io+$34
10) SP=402211d8 RP=74.000068e0 main_ci+$a0
11) SP=40221178 RP=74.00007450 PROGRAM+$218
12) SP=40221130 RP=74.00000000
(end of NM stack)
We again do a stack trace; this time the symbols for the program file show up.
$nmdat > loadinfo
nm SYS NL.PUB.SYS SID = $a
cm SYS SL.PUB.SYS
$nmdat > xl nl.build a nl.pub.sys
Preprocessing NL.BUILD.CMDEBUG, please wait ... Done
$nmdat > loadinfo
nm SYS NL.PUB.SYS SID = $a
nm SYS NL.PUB.SYS SID = $a
cm SYS SL.PUB.SYS
$nmdat >
We start by looking at our list of loaded files in DAT. We then proceed to map in a local copy
of an NL. Notice that there are now two entries for NL.PUB.SYS in the loaded file list both
at space $a. Attempts to look up symbols in space $a use the first entry in the table (which
corresponds to the file mapped with the PSEUDOMAP command). Likewise, attempts to
perform a name to address lookup for a symbol searches only the first NL.PUB.SYS entry.
Limitations, Restrictions
Information required to perform stack traces (the unwind tables) are also part of program
files and executable libraries. When a file is opened with this command, we should be
utilizing the unwind tables found there. This functionality is not implemented.
PURGEDUMP
DAT only
Purges a dump file.
Syntax
PURGEDUMP dumpfile