Debugging threads with HP Wilde Beest

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.
Issue 2:
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.
Thread- debugging in Attach Mode
HP WDB provides support to attach a running process to the debugger. To use thread
debugging commands after attaching GDB to a running process, complete the following
steps:
1. Set LD_LIBRARY_PATH to include the appropriate directory, by entering one of
the following commands:
• For 32 bit IPF applications,
export LD_LIBRARY_PATH=/opt/langtools/wdb/lib/hpux32
• For 64 bit IPF applications,
export LD_LIBRARY_PATH=/opt/langtools/wdb/lib/hpux64
• For 32 bit PA applications,
export LD_LIBRARY_PATH=/opt/langtools/wdb/lib
• For 64-bit PA applications,
export LD_LIBRARY_PATH=/opt/langtools/wdb/lib/pa20_64
2. Complete one of the following steps to preload the librtc runtime library:
• Set the target application to preload librtc by using the +rtc option for the
chatr command. In addition to automatically loading the librtc library,
the +rtc option for the chatr command also maps the shared libraries as
private.
To enable or disable the target application to preload the librtc runtime
library, enter the following command at the HP-UX prompt:
$ chatr +rtc <enable|disable> <executable>
Modes of Thread debugging in HP WDB 41