Debugging threads with HP Wilde Beest
In batch mode, the debugger detects the all the thread-conditions that are detected
during an interactive debugging session.
The debugger reports extended information such as variable address, name, id and
other specifications related to the involved pthread objects. In addition, it displays
the stack trace of the executing thread at the point of error.
Pre-requisites for Batch Mode of Thread Debugging
The various prerequisites for Batch mode of Thread Debugging are as follows:
• The thread-debugging feature in HP WDB is dependent on the availability of the
dynamic linker B.11.19 or later versions.
• Advanced thread-debugging feature requires the pthread tracer library which is
available by default on systems running HP-UX 11i v2 or later.
Steps to debug threads in Batch Mode
1. Compile the source files.
Set the LD_LIBRARY_PATH environment variable, based on the platform as follows:
• For IPF 32 bit applications, set
export LD_LIBRARY_PATH=/opt/langtools/wdb/lib/hpux32
• For IPF 64 bit applications, set
export LD_LIBRARY_PATH=/opt/langtools/wdb/lib/hpux64
• For PA 64 bit applications, set
export LD_LIBRARY_PATH=/opt/langtools/wdb/lib/pa20_64
2. Map the share libraries as private for HP 9000 systems using the following
command:
$ chatr +dbg enable ./executable
NOTE: This step is not applicable for Integrity systems.
3. Create a configuration file, rtcconfig to specify the various thread conditions
that you want the debugger to detect.
38