HP WDB GUI 5.8 Reference Manual ( February 2008 )
Debugging with WDB GUI
Advanced Thread Debugging Support
Chapter 382
Advanced Thread Debugging Support
WDB GUI 5.6 and later versions provide advanced thread debugging support to view the state
of pthread primitives in applications running on 11i v2, or 11i v3 operating systems. You can
view extended information on the state of threads, read-write locks, mutexes and conditional
variables.
Prerequisites for Advanced Thread Debugging in WDB GUI
The following pre-requisites apply for advanced thread debugging in WDB GUI:
• The advanced thread debugging features are supported for PA-RISC and Itanium
applications running on HP-UX 11i v2 and later versions of the operating system. HP
WDB GUI does not support thread debugging of PA-RISC applications on Integrity
systems
•The tracing pthread library is required for advanced thread-debugging. The pthread
tracer library is available by default on systems running HP-UX 11i v2 or later.
• The thread debugging feature in HP WDB is dependent on the availability of the Dynamic
Linker Version B.11.19.
•HP WDB GUI uses librtc.sl to enable thread debugging support. If the debugger is
installed in a directory other than the default /opt/langtools/bin directory, you must
use the environment variable, LIBRTC_SERVER, to export the path of the appropriate
version of librtc.sl.
• HP WDB GUI does not support debugging of programs that link with the archive version
of the standard C library, libc.a, or the core library, libcl.a. The programs must be
linked with libc.sl.
• For PA-RISC 32-bit applications, the dynamic library path look-up must be enabled for
advanced thread debugging. To enable dynamic library path look-up for advanced thread
debugging, enter the following command at HP-UX prompt:
# chatr +s enable <PA32-bitApp>
This command automatically enables dynamic library path look-up. No additional
environmental variables are required.
Support for info thread, info thread <thread-id> and set thread check
<on/off>
To view information on the state of the current threads in the application, complete the
following steps: