The Calls window has a toolbar that contains several buttons and has a shortcut menu with additional commands. For more information about setting the register context, see Register Context. You can set the register context to match a specific thread, context record, or trap frame. In kernel mode, the stack trace is based on the current register context. For more information about the stack of the current thread, see Controlling Processes and Threads. In user mode, the stack trace is based on the stack of the current thread. For more information about running to or from this point, see Controlling the Target. This action also changes the local context to the selected stack frame. 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. The following screen shot shows an example of a Calls window.īuttons in the Calls window enable you to customize the view of the call stack. To open the Calls window, choose Call Stack from the View menu. Calls WindowĪs an alternative to the k command, you can view the call stack in the Calls window. You can view the call stack by entering one of the k (Display Stack Backtrace) commands in the Debugger Command window. In WinDbg, you can view the call stack by entering commands or by using the Calls window. ISWIFT VIEW ENTIRE STACK TRACE HOW TOFor more information about how to change the register context, see Changing Contexts. The call stack that is displayed is based on the current program counter, unless you change the register context. The top function on the call stack is the current function, the next function is the function that called the current function, and so on. The call stack is the chain of function calls that have led to the current location of the program counter.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |