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 where command prints the call stack. For OpenMP slave threads, the command also prints the master thread's stack trace if the relevant frames are still active.
Print a procedure traceback.
Print the number top frames in the traceback.
Start traceback from frame number.
Print traceback as if fp register had address_expression value.
Include hidden frames.
Include library name with function name.
Quick traceback (only function names).
Verbose traceback (include function args and line info).
where:
number is a number of call stack frames.
Any of the above forms may be combined with a thread or LWP ID to obtain the traceback for the specified entity.
The -fp option is useful when the fp (frame pointer) register is corrupted, in which event dbx cannot reconstruct call stack properly. This option provides a shortcut for testing a value for being the correct fp register value. Once you have identified the correct value has been identified, you can set it with an assign command or lwp command.
Print a method traceback.
Print the number top frames in the traceback.
Start traceback from frame number.
Quick trace back (only method names).
Verbose traceback (include method arguments and line information).
where:
number is a number of call stack frames.
thread_id is a dbx-style thread ID or the Java thread name specified for the thread.