To view the dynamic state of a debugged application, just stop it at the point where you want to see its context. The debugger tools will automatically be popped up then, yielding the call stack of the application, as well as the state of the objects located in the object tree, which include at least the object corresponding to the level of the call stack where the call stack cursor is.

To see at which point the features in the call stack have stopped, just click the feature on which you want this information in the call stack. Doing this will change the cursor position in the call stack and display the flat view of the feature in the context tool.

To follow an object state between pauses of the application, pick and drop it into the object tree, which will make it stay in it.

You can also query features dynamically by using the evaluation tool, which can be very useful to have glimpses of the C memory of the system, for instance.

See Also:
Pausing an application
Call stack tool
Object tool
Evaluation tool

cached: 06/25/2017 12:55:43.000 AM