Debugging Core Files Using HP WDB

• 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.
NOTE:
• To avoid these limitations in debugging core files created by stripped binaries, you can use
the original unstripped version of the executable, if it is available. For more information
about debugging stripped binaries by using the symbol table from the unstripped version
of the executable, see “Debugging Core Files Created by Stripped Binaries (When the Symbol
Table is Available)” (page 20).
For an illustration of these limitations for core files created on an Integrity system, see “Sample
Debugging Session 3” in Example 5 (page 23).
22