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

Attaching to process <pid> failed.
Hint: Check if this process is already being traced by another gdb or other ttrace tools like caliper and
tusc.
Hint: Check whether program is on an NFS-mounted file-system. If so,you will need to mount the file system
with the "nointr" option with mount(1) or make a local copy of the program to resolve this problem.
Known issues
This section describes known issues in this release of HP WDB.
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++
• 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.
6 HP WDB 6.3 Release Notes