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

Limitations for Debugging Core Files Created by Binaries Compiled Without the -g
Option
The following limitations apply for core files that are created by binaries compiled without
the -g option:
• Argument information in the stack traces is not displayed.
• Local variables and type information are not displayed.
• Inline frame information is not displayed. The source line information is not displayed
for core files that are created by PA-RISC binaries.
In the case of Integrity systems (Itanium-based binaries), the source line information
is displayed for core files.
NOTE: In the case of core files that are created by Itanium-based binaries, the
source line information is available, irrespective of whether the binary is compiled
with the -g option, or not. To strip the line number information for Itanium-based
binaries, you must use the strip -l command orr the +nosrcpos linker option.
For an illustration of these limitations, see “Sample Debugging Session 2” in Example 5
(page 21).
Limitations for Debugging Core Files Created by Stripped Binaries
The following limitations apply for core files that are created by a stripped executable:
• Local variables and static variables in a stripped module are not displayed.
• Global variables and type information in a stripped module are not displayed.
However, the debugger can access the global or local variables (within the scope
of the variables) that are defined in other unstripped shared libraries, which are
loaded in to the stripped executable.
• Argument information in the stack traces is not displayed.
• The static function names appearing in the stack traces are not displayed. The
debugger may print random names instead of <unknown_procedure> while
displaying these function names.
• In the case of core files created by PA-RISC binaries, the function names (static and
non-static) appearing in the stack are not displayed.
Debugging Core Files Created by Optimized or Stripped Binaries 19