After you have started the VMC Debugger as described in the section Starting VMC Debugging, you have the following options for navigating to the desired information:
● By double-clicking a particular point in the output
● By entering commands in the command line
The figure below shows a possible initial screen for VMC Debugging. The red boxes show examples of where you could double-click to navigate or could enter a command:
The most important starting points for finding information in the VMC Debugger are listed below:
● The most frequently used commands are listed under available commands. You can execute these by double-clicking the relevant entry. You can also enter the commands in the command line at the bottom of the screen.
The function keys of the ABAP Debugger for these commands are also available in the VMC Debugger.
● Under Current stack of RFC server, you can double-click the frame number to display another frame.
● If you double-click a method argument or a local variable, the corresponding dump content is displayed:
In the case of complex variables, you can perform the forward/backward traversing by double-clicking a particular member (listed with “instance of”) and on a subarea name in the dump title bar.
● A list with threads is displayed under Thread Group main. You only need to double-click to go to a different thread.
● A list of active breakpoints is displayed under Breakpoints set. You can delete a breakpoint by double-clicking.
● Break when indicates a “conditional” breakpoint. When the program reaches the breakpoint position, the expression is evaluated. The program continues executing if the result is not “true”.
● You can use the Checkpoints menu to upload lists of predefined breakpoints, watchpoints, and exceptions from your local PC to the server, or to download them from the server to your PC.
If you enter the command checkpoints, the system displays the list on the screen. You can activate a selected checkpoint by double-clicking it.
Example of a checkpoint text file:
stop in com.sap.vmc.testapp.CommandHandler.handleRequest
stop at com.sap.vmc.testapp.CommandHandler:69 session == null