Known Problems and Workarounds

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.