User`s manual

296 digi.com Graphical User Interface
Stack (F12)
Select this option to activate or deactivate the Stack window. The Stack window
displays the top 32 bytes of the run-time stack. It also shows the line and column
at which the stack “snapshot” was taken. It is possible to scroll back to see the
progression of successive stack snapshots.
Dynamic C 9 introduced differences highlighting: each time you single step in C
or assembly, changed data can be highlighted in the Stack window. (This is also
true for the Memory Dump and Register windows.)
Execution Trace
(Alt+ F12)
Select Execution Trace to activate or deactivate the Execution Trace window.
The fields displayed in this window were specified in the Debugger dialog box
that is accessed via the Options | Project Options menu (see Enable execution
tracing).
The Trace window has a right-click pop-up menu. An option on this menu controls the display of an
additional column in the Trace window. If Group repeated statements is selected, the Show Repeat
Count may also be selected and will display in the rightmost column of the Trace window that comes
before the register contents column. A value displayed under Show Repeat Count is the number of
times the corresponding statement has been executed and, therefore, traced. The Timestamp column is
not updated for subsequent traces of a repeated statement.
The Group repeated statements option is useful when tracing statements inside a loop.
The rest of the pop-up menu options are more or less self-explanatory. You can choose to open the
source code for any function in the Trace window by selecting the function and choosing Open Source.
In the above screenshots, note that a trace statement for kbhit() is selected in the Trace window.
Choosing Open Source in this situation would open a window for STDIO.LIB, the library file that
contains the function kbhit().
You can also toggle auto scroll, as well as decide whether to display the complete path in the File Name
column. The last three menu options are for saving Trace window contents to another file. You can
select trace statements in the window and then using Copy selected traces or Copy with header you can
paste the selected traces anywhere you can perform a paste operation. You can also choose to copy the
entire contents of the current Trace window to a named file. This is similar to the option in the