Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Studio 12.3: Debugging a Program With dbx Oracle Solaris Studio 12.3 Information Library |
4. Viewing and Navigating To Code
5. Controlling Program Execution
6. Setting Breakpoints and Traces
8. Evaluating and Displaying Data
11. Debugging Multithreaded Applications
16. Debugging Fortran Using dbx
17. Debugging a Java Application With dbx
18. Debugging at the Machine-Instruction Level
19. Using dbx With the Korn Shell
20. Debugging Shared Libraries
The threads command lists all threads.
Print the list of all known threads.
Print threads normally not printed (zombies).
Controls whether all threads are printed or threads are filtered. The default is to filter threads. When filtering is on, threads that have been hidden by the thread -hide command are not listed.
Under the IDE, enables automatic updating of the thread listing.
Echo the current modes.
Each line of information is composed of the following:
An * (asterisk) indicating that an event requiring user attention has occurred in this thread. Usually this is a breakpoint.
An 'o’ instead of an asterisk indicates that a dbx internal event has occurred.
An > (arrow) denoting the current thread.
t@num, the thread id, referring to a particular thread. The number is the thread_t value passed back by thr_create.
b l@num meaning the thread is bound (currently assigned to the designated LWP), or a l@num meaning the thread is active (currently scheduled to run).
The “Start function” of the thread as passed to thr_create. A ?() means that the start function is not known.
The thread state, which is one of the following:
monitor
running
sleeping
wait
unknown
zombie
The function that the thread is currently executing.
Print the list of all known threads.
Print threads normally not printed (zombies).
Controls whether all threads are printed or threads are filtered. The default is to filter threads.
Under the IDE, enables automatic updating of the thread listing.
Echo the current modes.
Each line of information in the listing is composed of the following:
An > (arrow) denoting the current thread
t@number, a dbx-style thread ID
The thread state, which is one of the following:
monitor
running
sleeping
wait
unknown
zombie
The thread name in single quotation marks
A number indicating the thread priority