The following commands are available as backtrace support for thread debugging:
bt | The bt command provides the stack trace of the |
| current thread that is being executed or the thread |
| that accepts the signal in case of a core file. |
thread apply all bt | You can use the thread apply all bt command |
| to display the backtrace of all threads. The bt |
| command only provides the stack trace of the |
| current thread under execution. |
backtrace_other_thread | The backtrace_other_thread command prints |
| the backtrace of all stack frames for a thread with |
| stack pointer SP, program counter PC and address |
| of gr32 in the backing store BSP. This command |
| enables you to view the stack trace when the stack |
| is corrupted. When using this command, you must |
| ensure that the SP, PC, and BSP values are valid. |
| The syntax for the backtrace_other_thread |
| command is as follows: |
| backtrace_other_thread SP PC BSP |
Advanced thread debugging support is available for
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,
HP WDB 5.6 and later versions provide advanced
•The thread attempts to acquire a
•The thread attempts to unlock a mutex or a
•The thread waits (blocked) on a mutex or
•Different threads
•The thread terminates execution without unlocking the associated mutexes or
•The thread waits on a condition variable for which the associated mutex is not locked.
182