The current context is the portion of your program on which the debugger is focusing. One session is always current, unless no sessions are running. Within the current session, the thread from which the debugger regained control is the default current thread. Inside the current thread, the most recent call is the default current call. When you issue a debugging command, you are operating on the current context.
Most views in the Debugger window depend on the current context. For example, the Threads view shows the threads in the current session, while the Call Stack view shows the call stack for the current thread. The Local Variables view shows the variables that are local to the current call, and the Classes view shows the classes that have been loaded by the current session. When you change the current context, the contents of these views are updated to reflect the new context.
The exceptions are the Breakpoints and Watches views. These views list all breakpoints and watches set in the IDE. While the set of watches is shared by all sessions, an individual watch expression is evaluated and displayed based on the current context.
When a variable is active in the current context, the Source Editor displays the value of the variable when you move the pointer over it. In cases where a program includes different variables with the same name, the Source Editor displays the value based on the current context, and not on the instance of the variable in the source code.
The information displayed in the Debug Console and Program Output tabs in the Output window is tied to the current context.
See Also | |
---|---|
Debugger Window |