HP WDB 5.9 Release Notes

This occurs when GDB attempts a command line call on an already overflowing
thread stack.
Known Limitations
This section describes known limitations in this release of HP WDB.
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.
• You cannot specify an alternate output directory for the thread-error log. The
thread-error log file is output into the current working directory only.
• 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.
Debugger Support for Optimized Code
On PA-RISC systems for 32-bit and 64-bit applications, printing of local variable values
may be inaccurate for +O1 and higher optimizations.
NOTE: HP WDB 5.9 contains limited debugging support for optimized PA-RISC
32-bit applications and even more limited support for debugging optimized code (DOC)
on PA-RISC 64-bit applications. 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 2 lists the swinstall products for HP WDB.
Table 2 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 WDB
HP WDB GUI
If you install HP WDB GUI on a system where HP WDB has not yet been installed, HP
WDB is installed automatically.
16