HP WDB 5.8 Release Notes

is generated when the process stops at a system call, and the registers cannot be read by the
debugger. When the debugger calls the routine ttrace, it returns this warning.
• Error attaching WDB to a process that is traced by tools using ttrace
HP WDB cannot attach to a process that is traced by tools that use ttrace, such as Caliper,
adb, and tusc.
The debugger displays the following error message while attempting to attach to such a
process:
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.
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.
Installation Requirements and Compatibility Information
This section discusses the installation information for HP WDB.
Table 2 lists the swinstall products for HP WDB.
Known Issues 11