HP WDB 5.5 Release Notes

Introduction
Known Problems and Workarounds
Chapter 1
6
• Help text not updated for the info symbol command.
• WDB places global classes in local scope.
• Command line completion does not work in some scenarious.
• Native PA-RISC registers cannot be referenced by their architected name.
• PA-RISC 32-bit GDB core dumps while running in a core-file debugging session.
• GDB must restore the arg registers across frames.
• GDB prints floating value incorrectly when output radix is 8 or 16.
• Fortran failures detected on PA-RISC system when inline debugging is switched on.
• On PA-RISC systems GDB core dumps on heap corruption.
•The pxdb command does not run with q4p enabled.
• The info func shows the disassembly of the millicode function, but does not list the name.
•The packcore command fails if the recent libc patch is installed
• Unexpected warning, for signals.exp on PA-RISC 64-bit systems for +objdebug option.
• The add-symbol-file cannot load shared library or object files individually.
• Output files are generated during batch RTC in the wrong format.
• WDB failure due to incorrect function arguments.
• User friendly warning message to be issued when user tries to put breakpoint on routines in shared libraries.
• GDB does not step into a signal handler.
• Issue a meaningful message to user when info heap command is issued after the program exits.
• Message must be displayed for RTC_NO_ABORT before crashing due to corrupted memory.
• GDB does not accept command-line calls to overloaded function with incorrect argument type.
• PA GDB crashes on command-line calls
• pxdb64: warning: corrupted PD table
• More meaningful warning message required for pxdb on shared libraries.
• No demangled name associated with msymbol
• High water mark does not work on PA Status.
• Change infrtc.c to exit gracefully if detect 3rd party malloc.
• GDB ENOMEM without useful directives to user.
• 11.31 PA64 info heap arenas is incorrect.
Known Problems and Workarounds
This section describes known problems and suggested workarounds in this release of HP WDB.
• HP WDB 5.5 has no reported known problems.