Debugging threads with HP Wilde Beest

You can use the thread qualifier on conditional breakpoints as well; in this case, place
thread threadno before the breakpoint condition, like this:
((gdb)) break frik.c:13 thread 28 if bartab > lim
Whenever your program stops under GDB for any reason, all threads of execution stop,
not just the current thread. This allows you to examine the overall state of the program,
including switching between threads.
Conversely, whenever you restart the program, all threads start executing. This is true
even when single-stepping with commands like step or next.
Moreover, in general other threads stop in the middle of a statement, rather than at a
clean statement boundary, when the program stops.
You might even find your program stopped in another thread after continuing or even
single-stepping. This happens whenever some other thread runs into a breakpoint, a
signal, or an exception before the first thread completes the action you requested.
Advanced Thread Debugging Support
Advanced thread debugging support is available for multi-threaded applications
running on HP-UX 11iv2, or HP-UX 11iv3.
HP WDB 5.5 and later versions provide advanced thread debugging features to display
extended information on the state of pthread primitives such as mutexes, read-write
locks and conditional variables.
Enabling and Disabling Advanced Thread Debugging Features
The Advanced Thread Debugging features are available as options to the set
thread-check command. The syntax for the set thread-check command is as follows:
set thread check
The set thread-check command enables or disables advanced thread de-bugging.
This feature is off by default. The set thread-check command must be enabled
prior to running the application under the debugger, to force the underlying runtime
system to collect information on pthread primitives.
The advanced thread debugging features are available only if the set thread-check
command is set to on.
Prerequisites for Advanced thread debugging feature in HP WDB
• HP-UX 11i v2 and later versions of OS on both PA-RISC and Integrity systems
support the advanced thread debugging features.
• The thread debugging feature depends on the availability of the dynamic linker
B.11.19 and later versions.
• The advanced thread debugging commands work only if thread-check is set
to on.
Advanced Thread Debugging Support 17