Difference between revisions of "MC-Basic:ADDBREAKPOINT"

From SoftMC-Wiki
Jump to: navigation, search
m (Miborich moved page Axystems:MC-Basic:ADDBREAKPOINT to MC-Basic:ADDBREAKPOINT: Global renaming of Axystems: namespace into (Main):)
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
 +
{{Languages|MC-Basic:ADDBREAKPOINT}}
 
{{MC-Basic
 
{{MC-Basic
 
|SHORT FORM=
 
|SHORT FORM=
Line 42: Line 43:
  
 
|SEE ALSO=
 
|SEE ALSO=
* [[Axystems:MC-Basic:CLEARBREAKPOINT|CLEARBREAKPOINT]]
+
* [[MC-Basic:CLEARBREAKPOINT|CLEARBREAKPOINT]]
* [[Axystems:MC-Basic:CONTINUETASK|CONTINUETASK]]
+
* [[MC-Basic:CONTINUETASK|CONTINUETASK]]
* [[Axystems:MC-Basic:STEPIN|STEPIN]]
+
* [[MC-Basic:STEPIN|STEPIN]]
* [[Axystems:MC-Basic:STEPOUT|STEPOUT]]
+
* [[MC-Basic:STEPOUT|STEPOUT]]
* [[Axystems:MC-Basic:STEPOVER|STEPOVER]]
+
* [[MC-Basic:STEPOVER|STEPOVER]]
 
* [[AXY:MC-Basic:SERCMAXPOS|SERCMAXPOS]]
 
* [[AXY:MC-Basic:SERCMAXPOS|SERCMAXPOS]]
 
* [[AXY:MC-Basic:SERCMINPOS|SERCMINPOS]]
 
* [[AXY:MC-Basic:SERCMINPOS|SERCMINPOS]]
[[Category:Axystems:MC-Basic:Debug Tools|ADDBREAKPOINT]]
+
[[Category:MC-Basic:Debug Tools|ADDBREAKPOINT]]
 
}}
 
}}

Latest revision as of 03:03, 17 April 2017

Language: English  • 中文(简体)‎

This command inserts a breakpoint in the task or library functions/subroutines at the specified program line number. When the breakpoint is reached, the softMC halts execution of the task and sends a message to the host that the breakpoint has been reached.

When a breakpoint is reached, the task switches to the idle state. Program execution is resumed by issuing the CONTINUETASK command, or by using the program debugging commands: STEPIN, STEPOVER, and STEPOUT.

Short form

ABPoint

Syntax

AddBreakPoint <file name> <program line number> {<taskname>}

Availability

Up to 0. 4.2.1 version

Type

<program line number>: Long

Range

<file name>: Name of a task that is loaded in memory (May be program or library)
<program line number>: 1 to MaxLong
{<taskname>}: Name of program, using that is loaded in memory.

                             It's the option, what is useful for library, where taskname and file name are not the same. If the task name is not specified, breakpoint will be valid (global) for all the tasks that pass through the specified file and line.

Scope

Terminal

Limitations

Write only. The task must be loaded into memory.

Examples

AddBreakPoint MAKECUT.prg 20

AddBreakPoint user.lib 1001 mytask.prg

See Also