6 Debugging and Interactive Development
6.3 Keeping debugger windows up to date
It can be costly to keep all the panes of open debugger windows up to date. For this reason, Functional Developer only refreshes the information in debugger windows in certain circumstances.
Note: In the following descriptions, a window being "refreshed" can also mean the window being displayed for the first time, with up-to-date contents, if it has not yet been displayed.
- If an application thread pauses and a debugger window appears (or comes to the foreground), the debugger window for that thread is refreshed automatically.
- Threads pause when: there is an unhandled Dylan error in the thread, there was an out-of-language error in the thread, execution in the thread reached a breakpoint or step point, or the thread reached the end of an interactive evaluation.
- If you issue the pause command (Application > Pause or
)from a debugger window, that debugger window will be refreshed when the application pauses.
- If you issue the pause command from the project window or editor, the debugger for the application's master thread is refreshed.
In all of these circumstances, any other open debugger windows will not be refreshed unless you choose View > Refresh in them. If you choose View > Refresh All Debuggers, Functional Developer updates every open debugger window.
The Misc page of the debugger's View > Debugger Options dialog contains the option "Refresh all open debuggers when entering debugger". By default, this option is not set. When turned on, the rules above are ignored and every open debugger window is refreshed whenever the application pauses.