HP WDB v6.3 Release Notes (5900-2179, August 2012)

• librtc displays wrong names for functions in leak report.
• WDB 6.2 is unable to print addresses in a 32-bit process or core file. This occurs only when
the process has very large segments.
• Executing info heap <num> command for the first time before executing info heap
command displays incorrect result.
• info heap or info leak command fails to report realloc() call allocations using RTC.
• When debugging an application with retain_freed_blocks=on, RTC does not free the
data if the application goes out-of-memory either in batch mode or attach mode.
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 workaround is to
use the packcore command to obtain the core file and the involved load modules into the
system on which the debugging occurs.
• Debugging an attached process that is not compiled for debugging may generate warnings
On attaching the debugger to a program that is not compiled for debugging, the process may
stop in a system call and the following warning message about the various registers is
displayed:
No data warning: reading 'r3' register: No data warning: reading 'r4' register: No data
warning: reading 'r5' register: No data warning: reading 'r6' register: No data warning
This warning occurs when executing the step command, the backtrace command, or when
attempting to view the register information. To avoid this warning message, use the finish
command to execute the process until the system call returns. This warning message is generated
when the process stops at a system call, and the registers cannot be read by the debugger.
When the debugger calls the routine ttrace, it returns this warning.
• Error attaching WDB to a process that is traced by tools using ttrace
HP WDB cannot attach to a process that is traced by tools that use ttrace, such as Caliper,
adb, and tusc.
The debugger displays the following error message while attempting to attach to such a
process:
Known problems and workarounds 5