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

Limitations for batch mode heap debugging
On PA-RISC systems, the batch mode memory debugging might fail if the application uses atfork
handlers. This issue is resolved in HP WDB 6.1 onwards on Itanium systems.
Batch mode thread debugging
• The feature does not obtain the thread-error information in batch mode for forked process in
a multiprocessing application. However, if the librtc.sl library is pre-loaded, the debugger
obtains the thread-error information in the batch mode for exec-ed application.
• HP WDB cannot execute both batch mode thread check and batch mode heap check together.
If the rtcconfig file has both entries, then batch heap check overrides the batch thread
check.
Mixed mode debugging
The following are not supported for mixed mode debugging:
• Placing a breakpoint on a PA-RISC library.
• Listing the arguments (using the info args command) for a selected PA-RISC frame during
corefile debugging. Alternatively, the disassembly instructions or runtime conventions can be
examined to identify the locations of the arguments and the values at these locations can be
displayed using the print or x command.
• Printing the local variables of the selected frame (using the info locals command) for a
selected PA-RISC frame during corefile debugging. Alternatively, the disassembly instructions
can be examined to identify the locations of the arguments and the values at these locations
of the local variables can be displayed using the print or x command.
• Executing the backtrace_other_thread command for a frame belonging to a PA-RISC
library.
• Executing the maint info unwind command for PA addresses.
• Printing the description of the type of expression or data type (using the ptype command)
on a PA-RISC symbol.
Debugger support for optimized code
On HP 9000 systems for 32-bit and 64-bit applications, printing of local variable values may be
inaccurate for +O1 and higher optimizations.
NOTE: HP WDB 6.1 and later versions contains limited debugging support for optimized code
of 32-bit applications on HP 9000 and even more limited support for debugging optimized code
(DOC) for 64-bit applications on HP 9000 systems. Additionally, the debugging support becomes
limited as higher levels of compiler optimization are used.
Installation requirements and compatibility information
This section discusses the installation information for HP WDB.
Table 1 lists the swinstall products for HP WDB.
Table 1 HP WDB Installation
DescriptionProduct Name
HP WDB -The HP implementation of the open source
debugger GDB
HP WDB
Optional graphical user interface component for HP WDBHP WDB GUI
Installation requirements and compatibility information 7