Debugging Core Files Using HP WDB (5900-1573; WDB 6.2; January 2011)

Table 2 Commonly Used Commands for Core File Debugging (continued)
DescriptionCommand
Debugging
Feature
Unpacks the tar file that is generated by the packcore
command so that the debugger can use the executable
and shared libraries from this bundle, when debugging
the core file on a different system from the one on which
the core file was originally created.
unpackcoreUnpacking the
core file along
with the
associated
shared
libraries
Enables you to examine a packcore directory, which
was previously created by unpackcore. It takes one
optional argument, which is the name of the packcore
directory.
getcore
<packcore-directory>
Examining a
core file which
was previously
created by
unpackcore
Enables or disables the limitation on the number of frames
to be unwound. This command is available in HP WDB
6.0 and later versions. By default, the number of frames
to be unwound is set to 10000 so that WDB does not
run out-of-memory. If this command is set to on, WDB
unwinds frames beyond 10000 frames. Setting this
command to off, disables the limitation on the number
of frames.
set unwind-all-frames
[on|off]
Unwinding
frames
beyond
10000 frames
Example 8 (page 40) and Example 9 (page 48) illustrate the use of the common core
file debugging commands.
What is a Symbol Table?
A symbol table is a set of records that define the set of visible and important symbols in
a program. These symbols are stored in the program. Each (unstripped) program has
an associated symbol table.
The nm command displays the symbol information for a specified object file.
Example 4 illustrates how to view symbol information for an object file by using the nm
command for an object file, on an HP 9000 system.
16