HP WDB 5.9 Release Notes

Known Problems and Workarounds
This section describes known problems and the suggested workarounds in this release
of HP WDB.
• Debugging an attached process that is not compiled for debugging may generate
warnings
On attaching the debugger to a program that is not compiled for debugging, the
process may stop in a system call and the following warning message about the
various registers is displayed:
No data warning: reading 'r3' register: No data warning: reading 'r4' register: No data
warning: reading 'r5' register: No data warning: reading 'r6' register: No data warning
This warning occurs when executing the step command, the backtrace
command, or when attempting to view the register information. To avoid this
warning message, use the finish command to execute the process until the system
call returns. This warning message 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!
Known Problems and Workarounds 15