Debugging Tools for Windows

Calls Window

The Calls window displays the current call stack information.

Opening the Calls Window

To open or switch to the Calls window, in the WinDbg window, on the View menu, click Call Stack. (You can also press ALT+6 or click the Calls (Alt+6) button () on the toolbar. ALT+SHIFT+6 will close the Calls Window.)

The following figure shows an example of a Calls window.

The Calls window displays the call stack information in several columns, most of which can be visible or hidden. If none of the optional columns are visible, only the name or offset of each function is displayed.

Using the Calls Window

To move to the corresponding call location in the Source window or Disassembly window, double-click a line of the call stack, or select a line and press ENTER. This action also changes the local context to the selected stack frame. For more information about running to or from this point, see Controlling the Target.

In user mode, the stack trace is based on the stack of the current thread. For more information about the stack of the current thread, see Controlling Processes and Threads.

In kernel mode, the stack trace is based on the current register context. You can set the register context to match a specific thread, context record, or trap frame. For more information about setting the register context, see Register Context.

Toolbar and Shortcut Menu

The Calls window has a toolbar that contains several buttons and has a shortcut menu with additional commands. To access this menu, right-click the title bar or click the icon near the upper-right corner of the window (). The toolbar and menu contain the following buttons and commands:

Additional Information

For more information about stack traces and for other ways to display stack traces, see Viewing the Call Stack. For more information about the register context and the local context, see Changing Contexts. For more information about docked, tabbed, and floating windows, see Positioning the Windows. For more information about all techniques that you can use to control debugging information windows, see Using Debugging Information Windows.

Build machine: CAPEBUILD