skip to main content

Debugger : Debugger Functions

Debugger Functions
The following is a list of available debugger functions, how they are accessed, and their descriptions:
Display data as hexadecimal sets the default value for the Hex flag in the following dialogs:
Monitor default enabled state specifies if new monitors will be enabled or not by default.
Variable hint delay sets the delay in milliseconds for the tool-tip on data-item values.
Repeats the last command entered in the Command Area. The command is not immediately executed, so the user can change it before executing.
Usage: b0 [-d] ProgramName
Usage: break
Usage: break [-d] { LineNumber | ParagraphName } [SourceCode] [when WhenConditions]
Sets a breakpoint. When "-d" is specified, the breakpoint is disabled.
LineNumber is the line number to which the breakpoint refers. That line must contain a statement. If a statement is split between several lines, the breakpoint can only be set at the first line.
ParagraphName is the name of a paragraph. The breakpoint will refer to its first line.
SourceCode is the optional name of the source code to which LineNumber and ParagraphName refer. If SourceCode is not specified, the current source code is implied.
WhenConditions is: [-x][-env] VariableName Operator Value [LogicalOperator VariableName Operator Value] ...
       VariableName is the data item to monitor.
       Operator can be =, !=, <, >, <=, >=.
       LogicalOperator can be either && or II.
       Value is the value to be tested.
       if -x is used, the value is hexadecimal
       if -env is used, the variable is searched for amongst configuration properties
Usage: break -l
Activates the Breakpoint view in the Information Window. All breakpoints currently set are listed.
Usage: clear { LineNumber | ParagraphName } [SourceCode]
LineNumber is the line number where the breakpoint is set.
ParagraphName is the name of the paragraph where a breakpoint is set.
SourceCode is the optional name of the source code that LineNumber and ParagraphName refer to. If SourceCode is not specified, the current source code is implied.
Usage: clear -l
Usage: continue
Usage: directory [DirectoryName]
If DirectoryName is omitted, then the current debugger code prefix is shown. Otherwise, the directory specified by DirectoryName is added to the debugger code prefix. See iscobol.debug.code_prefix for more information on the debugger code prefix.
Usage: display
Usage: display [-x] [-tree] VariableName
VariableName is the data item whose value will be displayed.
Usage: display ControlHandle [ property | prop ] PropertyName
ControlHandle must refer to a valid handle.
PropertyName is a the name of a property of ControlHandle.
Usage: display -classversion
Usage: display -env VariableName
VariableName is the name of the environment variable to be displayed.
Usage: env VariableName
VariableName is the name of the environment variable to be displayed.
Usage: fb SearchText
SearchText is the text to be searched for.
Usage: ff SearchText
SearchText is the text to be searched for.
Usage: ft SearchText
SearchText is the text to be searched for.
Usage: help DebuggerCommand
DebuggerCommand is the command to be searched for.
Usage: jump line-number [filename]
Note: Jumping to lines that are inside blocks is not allowed. In this case the Debugger jumps to the beginning of the block.
Usage: jump paragraph-name
Usage: jump -outpar
Usage: jump -outprog
Usage: length variable-name
Usage: let [-x] VariableName=VariableValue
When "-x" is specified, a hexadecimal value must be entered.
VariableName is the data item whose value will be changed.
VariableValue is the value that will be set to VariableName.
Usage: let ControlHandle [ property | prop ] PropertyName=PropertyValue
ControlHandle must refer to a valid handle.
PropertyName is a the name of a property of ControlHandle.
PropertyValue is the value that will be set to PropertyName.
Usage: let -env VariableName=VariableValue
VariableName is the data item whose value will be changed.
VariableValue is the value that will be set to VariableName.
Usage: m0 [-d][classname][methodname]([signature])
If classname is not specified, the breakpoint is set on the current debugged class. If signature is not specified and there is only a method named methodname, the breakpoint is set on that method. signature is a comma separated list of class names or primitive types names,
Usage: monitor
Usage: monitor [-d] [-e] [-x] VariableName [ when Operator Value | always | never ]
VariableName is the data item to monitor.
Operator can be =, !=, <, >, <=, >=.
Value is the value to be tested. If you need to include leading or trailing spaces in the value, delimit it by quotes.
When "-d" is specified, the monitor is disabled and its value in the Information Window is not updated.
When "-e" is specified, the monitor is enabled and its value in the Information Window is updated.
When "-x" is specified, the value is hexadecimal.
When the "always" phrase is specified, the debugger is activated each time the value changes.
When the "never" phrase is specified, the debugger is never activated, but the value in the Information Window is always updated.
Usage: monitor [-d][-e] ControlHandle [ property | prop ] PropertyName [ when Operator PropertyValue | always | never ]
ControlHandle must refer to a valid handle.
PropertyName is a the name of the property of ControlHandle to monitor.
Operator can be =, !=, <, >, <=, >=.
PropertyValue is the value to be tested.
When "-d" is specified, the monitor is disabled and its value in the Information Window is not updated.
When "-e" is specified, the monitor is enabled and its value in the Information Window is updated.
When the "always" phrase is specified, the debugger is activated each time the value changes.
When the "never" phrase is specified, the debugger is never activated, but the value in the Information Window is always updated.
Usage: monitor [-d][-e] -env VariableName
When "-d" is specified, the monitor is disabled and its value in the Information Window is not updated.
When "-e" is specified, the monitor is enabled and its value in the Information Window is updated.
VariableName is the name of the environment variable to monitor.
Usage: monitor -l
Executes the current statement. If it is a PERFORM statement, it is entirely executed.
Usage: offset variable-name
Usage: outpar
Usage: outprog
Usage: pause
Usage: readsession [FileName]
Usage: step [n]
Executes the current statement. If it is a PERFORM statement, the first statement of the paragraph or session that it refers to becomes current. If n is specified and it’s greater than 1, the step command is automatically repeated n times.
Usage: stoff
Usage: thread ThreadName
ThreadName is the name of the thread to activate.
Usage: thread -l
Activates the Threads view in the Information Window. All monitors currently set are listed.
Usage: to LineNumber [SourceCode]
LineNumber is the line to reach.
SourceCode is the optional name of the source code to which LineNumber refers. If it is not specified, the current source code is implied.
Usage: troff
Usage: unmonitor VariableName
VariableName is a monitored data item.
Usage: unmonitor [-env] VariableName
VariableName is a monitored environment variable .
Usage: unmonitor -a
Usage: writesession [FileName]
FileName is the name of the file that contains the debugger configuration. If it is not specified, 'ISCONTROLSET.isd' is implied.
Enter Debugger
If a program compiled in debug mode is performing ACCEPT of user input on a graphical window, if you press Pause/Break on the keyboard, you will enter Debugger at the next ACCEPT interruption. For example, if you want to debug what happens when you click on a specific push-button of your window,
1.
2.
3.
4.
5.
6.
On some keyboards the Pause/Break key is not available. In order to have the same feature associated to another key, set the exception value of that key to 65535. For example, if you want to enter debugger using F6, start the Debugger as follows:

Copyright (c) 2017 Veryant
Contact us
Please share your comments on this manual or on any
Veryant product documentation with the email button at the top left