HP WDB 6.2 Release Notes (5900-1472; January 2011)

Smarter Printing of Function Pointers
WDB is made smarter now in printing the function pointers. It now decodes extra level
of indirection for the programmer’s convenience.
More Intuitive Leak Reports
A note will be appended to every memory debugging report providing more details for
function names displayed as ???.
Debugging with Debug Information Available In the Side Debug File
From version B.12.56, the HP-UX/Integrity linker has added an option +dbgfile
<path>. This option enables you to emit debug information separately to the file specified
by 'path', instead of the target executable/library. Gdb supports debugging from the
side debug file, produced with the +dbgfile linker option.
NOTE: This feature is currently supported only on HP Integrity systems.
Support for mmapfile Command
HP-UX does not include mmap-ed regions with MAP_SHARED mappings or MAP_PRIVATE
with Read-Only permission in core. With the mmapfile command of gdb, you can add
mmap-ed sections while debugging core files. This can be done during the debug session
of the core file, helping you to debug using the memory contents from the missing mmap-ed
regions in core file.
NOTE: This feature is currently supported only on HP Integrity systems.
Patches and Defect Fixes in HP WDB 6.2
The following defects are fixed in HP WDB 6.2:
• Gdb shows extra signal 0 on interruption, when attached to a process from another
shell.
• Gdb cannot print <file_name>::<variable> correctly for both global and
static variables under certain conditions.
• Gdb cannot resolve symbol names and backtraces for ILP32 binaries with text
segment size > 1 GB.
• Gdb shows wrong line numbers for some functions for ILP32 binaries with text
segment size > 1 GB.
• Gdb sometimes does not execute step/next commands properly for ILP32 binaries
with text segment size > 1 GB.
• Gdb shows bad argument values for some functions for ILP32 binaries with text
segment size > 1 GB.
Patches and Defect Fixes in HP WDB 6.2 5