Selecting an Application for Debugging
There are two ways to select applications for debugging:
Click the application’s name/link in the Applications section of the System Summary (see Source Debugger: Summary (Live) Tab).
OR
1. Within the VTS application, navigate to the page whose source code you wish to examine.
2. Click the Select Window to Debug button.
3. Click on the appropriate window in your VTS application. The Source Debugger will select the running module instance that contains the graphic statement under the mouse pointer as the current module instance, and will display the module trees, content list, and source code for that module window.
You can select an application that is not running for debugging using the first option (above). Simply click the name of the application in the Stopped section of the Applications section of the System Summary. You will not see modules listed in the Modules section, as none will be loaded and running. You can place a break point on a non-loaded application, and then run it, however, you must generate debug symbols for this to occur.
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.
Each time you navigate to a different module in the module tree, or select a new window in your VTS application for debugging, the Source Debugger will change the currently selected module instance accordingly in the module trees, module content window, and code display. If the source file containing the currently selected module has not yet been displayed by the Source Debugger, a new tab will be added to the source code window and made the current tab. You may click any tab at any time to view the code for a different source code file. You may use the forward and back tool bar navigation buttons, or the corresponding keyboard shortcuts to move backwards and forwards through the module instances that you have selected and viewed.
Each application runs in its own debugger section. The title bar identifies which is being debugged. The Source Debugger runs one session per application or crash dump file being debugged. Once the application has been selected, the session is committed. There is a new, independent session for each.