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

• Gdb does not detect core file and executable mismatch and sometimes crashes in
dld.
• User disabled watchpoint gets wrongly re-enabled automatically.
• Gdb sometimes wrongly gives out a message that the target program received
SIGSEGV, when a misaligned load is retired and a wacthpoint is set.
• Gdb sometimes crashes after watchpoint is set on local variable.
• Gdb crashes if the application has mangled names with anonymous namespace
<unnamed namespace>, not followed by the scope resolution operator ::
• $ gdb -e <program name> cannot load symbols and allow the process to run.
• Wdb runs out of memory on HP 9000 servers and crashes on Integrity servers for
Fortran programs during the application run, when the debug information for function
parameters contains incorrect memory addresses.
• Wdb dumps core when debugging a C++ program on HP-UX 11.23 Integrity
systems, when a typeinfo mangled name does not contain a variable name.
Known Problems and Workarounds
This section describes known problems and the suggested workarounds in this release
of HP WDB.
• The find command does not search the entire memory.
The HP WDB find command does not search the pattern in the entire memory
address range starting from 0x0 to 0xff..ff. It displays the following warning
message:
(gdb) find 010,0xffffffffffffff,"hello"
warning: Unable to access target memory at 0x8, halting search.
Pattern not found.
• Performance Degradation in Memory Debugging
For 64-bit applications on HP-UX 11i v2 and later on Integrity systems, heap check
performance degrades when the string option is set in the set heap-check
command:
set heap-check string on
• Incorrect usage of . and -> while printing the values for C++ applications
WDB allows users to interchangeably use "." and "->" while printing values for
C++ applications. WDB incorrectly allows users to use "." with a pointer variable
and "->" with a reference variable while printing the value for C++ applications.
• Mismatch Between dld.so Libraries Causes Issues
A mismatch in the dld.so libraries available in the core file and in the system might
cause issues in unwinding beyond some frames within the libc.so library. The
6 HP WDB 6.2 Release Notes