Go to main content
Oracle® Developer Studio 12.6: Debugging a Program with dbx

Exit Print View

Updated: June 2017
 
 

where Command

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.

Native Mode Syntax

where

Print a procedure traceback.

where number

Print the number top frames in the traceback.

where –f number

Start traceback from frame number.

where –fp address-expression

Print traceback as if fp register had address-expression value.

where –h

Include hidden frames.

where –l

Include library name with function name.

where –q

Quick traceback (only function names).

where –v

Verbose traceback, which includes the function arguments and line information.

where:

address-expression is any expression resulting in or usable as an address.

number is a number of call stack frames.

Any of these options can 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 that the correct value has been identified, you can set it with an assign command or lwp command.

Java Mode Syntax

where [thread-ID]

Print a method traceback.

where -f [thread-ID] number

Print the number top frames in the traceback.

If f is specified, start traceback from frame number.

where -q [thread-ID]

Quick trace back (only method names).

where -v [thread-ID]

Verbose traceback, which includes the 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.