WDB Release Notes (769152-001, March 2014)

Batch mode thread debugging
• During the execution of advanced thread checking for applications that fork, in the interactive
mode, the following message appears if the GDB follows the child:
Pthread analysis file missing!
This error message appears because the thread-error information for the forked process is not
available. However, if the forked process exec() s another binary, the thread-error information
is available for the exec-ed binary.
• In both interactive and batch modes, if the applications exceed their thread stack utilization,
the following error message appears:
Error accessing memory address!
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 register
information being displayed. Alternatively, execute the info reg command 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++
• HP WDB is unable to hit breakpoints placed on constructors in case of multiple inheritance.
• HP 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, HP WDB may not print values of local
variables for outer or parent procedure inside its internal subroutine.
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.
Known limitations 7