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

NOTE: Following are different ways of representing the /size-char and
/max-count parameters:
/1b
/b1
/b /1
/1 /b
where:
1 Specifies that find must display 1 matching pattern.
b Specifies that the size of the pattern is 8 bits.
Displaying run time type information
HP WDB enables you to view the run time type information for C++ polymorphic objects.
The following command displays the run time information for C++ polymorphic object.
info rtti <address>
The input to this command is address of the C++ polymorphic object. GDB displays
de-mangled type name as output.
NOTE: This command is supported only on Integrity systems.
Debugging PA-RISC Core Files on Integrity Systems
Using WDB, you can transparently debug PA-RISC programs running in compatibility
mode under Aries on Integrity systems.
To debug a core file generated by a PA-RISC program on an Integrity system, complete
the following steps:
1. Transfer the executable program, core file, and all shared libraries that are used by
the PA-RISC application, to the target Integrity system.
2. Set the GDB_SHLIB_PATH environment variable to a colon-separated list of directory
path names on the system where the transferred shared libraries reside.
3. Use WDB to examine the core file on the Integrity system.
Avoiding Core File Corruption
You can prevent overwriting of core files from a different process by setting the kernel
to store the core file in a process-specific file name, <core.pid> (where pid is the
process ID of the process that dumped the core).
Displaying run time type information 33