Troubleshooter Debugger Tab

From Lianjapedia
Jump to: navigation, search

Under Construction. Coming soon in Lianja v5.0

The Troubleshooter

The Troubleshooter provides a tabbed interface bringing together debugging, tracing and performance metrics to assist you in testing and tuning your Apps.

Troubleshooter


The Debugger Tab

The Debugger Tab contains the Lianja/VFP Debugger. The tabbed upper container contains an Output panel and the files currently loaded in the Debugger. The lower tabbed container contains the following:

  • Command Window
  • Breakpoints Grid
  • Watches Grid
  • Call Stack Grid
  • Globals Grid
  • Locals Grid

Below these are a message line showing the current operation and an actionbar.

Activating the Debugger

As with all Troubleshooter tabs, the Debugger Tab can be selected by clicking on its tab.

It can also be opened in the following ways:

Loading Files in the Debugger

Programs containing the debugger command or specified with the debug <prg-filename> or debugger <prg-filename> commands are automatically loaded into the debugger when the command is issued.

Programs can also be loaded from the Apps Workspace. Open the file (double-click the filename) in the Script Editor then click the Open file in Debugger toolbutton.

Open file in Debugger


Library files can be loaded from the Library Workspace in the same way: open the file (double-click the filename) in the Script Editor then click the Open file in Debugger toolbutton.

Select the Debugger Tab or click Debug in the Modebar then click Run/Continue in the actionbar to debug the file.

Debugger Tab


Note: if multiple files are loaded, the file in the leftmost tab will be debugged when Run/Continue is clicked.

Called programs are automatically loaded when referenced by a program being debugged and Step Into is clicked.

Right-clicking in a loaded file displays the context menu:

Debugger Tab


Note: some menu options only operate when the file is in edit mode. See actionbar below for how to switch mode.

While the debugger is active, hovering the mouse over a command, function, field or variable will display its Intellitip with information about its usage, syntax or definition. For more about Intellitips and other Lianja CodeAssistant for Lianja/VFP features, see Script Editor: The Lianja CodeAssistant.

Debugger Tab


Output

The Output panel displays program and Command Window output.

Debugger Tab


Right-clicking in the Output panel displays the context menu:

Debugger Tab


Command

The Debug Console contains a Lianja/VFP Command Window. All Lianja/VFP commands and functions can be used in the Command Window apart from flow control and looping commands and others that form a begin...end statement block.

Note also, as in the floating Command Window and Console Workspace:

  • The semi-colon ';' line continuation character is not supported.
  • & macro substitution is supported.

Output is displayed in the Output panel; errors are reported in the Error Viewer Tab.

Breakpoints

Breakpoints cause execution of the running program to pause before the line of code set as a breakpoint is run or when the condition of a conditional breakpoint evaluates to true.

To set a conditional breakpoint, click Add Conditional Breakpoint in the actionbar and enter the condition in the dialog that is displayed.

Debugger Tab


Line breakpoints can be set and unset using the actionbar or by clicking in the line number column to the left of the selected line.

Debugger Tab


The Breakpoints grid shows the filename and line number for currently set breakpoints. Double-clicking on a grid row will clear that breakpoint.

Click Remove All Breakpoints in the actionbar to clear all current breakpoints.

Debugger Tab


Watches

Watches (or 'watchpoints') cause execution of the running program to pause after the value of a field or memory variable set as a watchpoint changes. Watches are set using the actionbar:

Debugger Tab


The Watchpoints grid shows the name, data type and current value for currently set watchpoints. Double-clicking on a grid row will clear that watchpoint.

Debugger Tab


Click Remove All Watches in the actionbar to clear all current watchpoints.

Debugger Tab


Call Stack

The Call Stack grid shows the filename and line number for each program in the current stack.

Debugger Tab


Globals

Locals

Actionbar

Action Description
Run/Continue Run or continue running the program to the next breakpoint or watchpoint or to the end if no breakpoints or watchpoints are set.
Stop Stop debugging.
Edit Code Put the currently selected file into edit mode.
Save Code Displayed when edit mode (Edit Code above) has been selected. Click to save any changes and exit edit mode.
Revert Code Displayed when edit mode (Edit Code above) has been selected. Click to cancel any changes and exit edit mode.
Refresh all files Refresh all files in the debugger. This will update them with any changes made using the Script Editor in the Apps Workspace or Library Workspace.
Step Over Move to the next line of code without running the current line.
Step Into Run the current line of code then move to the next line.
Step Out Run until returning to the calling program, then move to the next line.
Add Conditional Breakpoint Set a conditional breakpoint on a specified condition. A dialog will be displayed so the condition can be entered.
Toggle Breakpoint Set a breakpoint on the current line, or unset the breakpoint if one already exists.
Toggle Watch Set a watchpoint on the currently selected variable or field, or unset the watchpoint if one already exists.
Remove All Breakpoints Remove all breakpoints.
Remove All Watches Remove all watchpoints.
List Status List the current data environment in the Output window.
List Memory List the current memory variables in the Output window.
List Structure List the structure of the currently selected table or cursor in the Output window.
Clear Clear the Output window.

See Also

Command Window, Error Handling and Debugging, Script Editor