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

This occurs when GDB attempts a command line call on an already overflowing

thread stack.

Mixed Mode Debugging

Following are known issues in mixed mode debugging:

• Listing of registers currently in use for PA-RISC 32-bit shared library frames causes

the unswizzled 32-bit values to be displayed.

• Clicking on the registers tab for a PA-RISC frame in the WDB-GUI results in incorrect

at the gdb prompt in the Commands tab.

• For a signal handler invoked while executing in a PA-RISC routine, when the info

frame command is run on the signal handler called frame, the saved

libaries32.so IP address is displayed, rather than the PCOQH value of the

PA-RISC routine.

• Printing the value of a floating point register using the print command does not

work. The info reg command must be used.

NOTE: If an application crashes in the aries signal handler, the debug-aries option

is turned on by default and only the libaries frames are displayed.

Known Limitations

This section describes known limitations in this release of HP WDB.

Limitations for C++

• WDB is unable to hit breakpoints placed on constructors in case of multiple

inheritance.

• WDB is unable to make command-line calls to string methods when there are no

calls to these methods from the application.

• In Fortran programs containing nested procedures, WDB may not print values of

local variables for outer or parent procedure inside its internal subroutine.

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

8 HP WDB 6.2 Release Notes