Debugging threads with HP Wilde Beest

Stack trace Stack trace is a summary of the stack frames. These stack frames contain the function
calls which the program initiates during its execution.
Thread Debugging commands at a glance
Table 2 Thread Debugging Commands
DescriptionCommand
Enables or disables Advanced thread debugging
feature. The default setting is off.
set thread-check on/off
Displays a list of known threads.
info-thread[thread-id]
Displays a list of known mutexes.
info mutex[mutex-id]
Displays a list of known conditional variables.
info condvar[condvar-id]
Displays a list of known read-write locks.
info rwlock[rwlock-id]
Checks if a thread attempts to acquire a
non-recursive mutex that it currently holds.
set thread-check
recursive-relock[on|off]
Checks if any thread has used more than the
specified percentage [num] of the stack location.
set thread-check stack-util[num]
Checks if the number of threads waiting on any
pthread objects exceeds the specified threshold
number.
set thread-check num-waiters[num]
Checks if a thread has terminated execution without
joining or detaching the thread.
set thread-check
thread-exit-no-join-detach[on|off]
Checks if a thread has attempted to unlock a mutex
or a read-write block that it has not acquired.
set thread-check
unlock-not-own[on|off]
Checks if a thread waits on a mutex or a read-write
lock that is held by a thread with a different
scheduling policy.
set thread-check
mixed-sched-policy[on|off]
Checks if an application uses the same condition
variable in multiple calls by different threads.
set thread-check
cv-multiple-mxs[on|off]
Checks if the associated mutex of a condition
variable is locked when the thread calls the
pthread_cond_wait() routine.
set thread-check cv-wait-no-mx[on|off]
46