Using the Source Debugger

The Source Debugger is a script application included with VTS. Before you can run the Source Debugger, you must first add it to the VAM. To do so, follow the directions included in Adding Existing Applications to the VAM.

Once the Source Debugger application has been added to the VAM, you may run it by selecting it in the VAM's Available Applications list, and clicking the Run button.

Note: Applications that are to be debugged using the Source Debugger need to have additional information generated at compile time to allow the Source Debugger to map in-memory modules to source code. These "symbolic" reference files are generated by clicking the VAM's "Properties" button, and selecting the "Generate Debug Symbols" checkbox featured on the "Application Properties" dialog. You must then re-compile the entire application. Enabling the generation of symbolic references for the Source Debugger does not alter the generated module code, but reduces compilation speed. For production code, you can generate a set of debug symbols (held in .SYM files in your application directory), and simply archive them with your set of VTS application source code files. Later, if you should discover a problem on a production machine (that just contains the .RUN files produced by the compiler), you can simply copy the source and symbol files to the application directory on the target machine and use the full capabilities of the Source Debugger. If you do not have a set of .SYM file, you can still use the Source Debugger, but you will not be able to place breakpoints or position the source code for the currently selected module accurately.

Topics in this section:

Selecting Applications and Files for Debugging

Dump Files

Examining Code Paths Using Thread Display

Working with Breakpoints and Data Breakpoints

Working with Watches

Working with Variables, Arrays, Pointers, Constants, and Parameters

Working with Modules

Copying and Pasting Code Using the Source Debugger

Source Debugger Options

Code Coverage