The stack/status window

This window can be brought to the top by pressing Alt+C in any other window. The stack/status window provides two uses:

• to display the reason why SDBG has been entered.

• to display the current call stack,

The status part of this window gives the reason that SDBG has been entered.

The stack part gives a trace back through the active call stack. This is a list of the active subroutines and functions. Routines that have debugging information, and therefore can be debugged at the source code level, are displayed in black text. Routines having no debugging information are shown in grey text. You can view the source code and variables for any routine in the call stack with debugging information by either:

• moving the bar in the status window to the line containing the routine name and pressing Enter,

• or by double-clicking the left mouse button over the routine name.

If you try to open a routine with no debugging information a machine code window will appear. This may appear confusing if you are not familiar with programming at this low level. If one appears, simply click the close button or press Escape and it will disappear.

The stack/status window does not have a close button and cannot be closed. This is because the current call stack and status are always relevant.

There are some key presses that apply to every window.

They are as follows: