Breakpoints can be set in any Octave function, using the
Set a breakpoint in function func.
Function name as a string variable. When already in debug mode this should be left out and only the line should be given.
Line number where the breakpoint should be set. Multiple lines may be given as separate arguments or as a vector.
When called with a single argument func, the breakpoint is set at the first executable line in the named function.
The optional output rline is the real line number where the breakpoint was set. This can differ from specified line if the line is not executable. For example, if a breakpoint attempted on a blank line then Octave will set the real breakpoint at the next executable line.
See also: dbclear, dbstatus, dbstep, debug_on_error, debug_on_warning, debug_on_interrupt.
Note that breakpoints cannot be set in built-in functions
sin, etc.) or dynamically loaded function (i.e., oct-files). To
set a breakpoint immediately on entering a function, the breakpoint
should be set to line 1. The leading comment block will be ignored and
the breakpoint will be set to the first executable statement in the
function. For example:
dbstop ("asind", 1) ⇒ 29
Note that the return value of
29 means that the breakpoint was
effectively set to line 29. The status of breakpoints in a function can
be queried with the
Report the location of active breakpoints.
When called with no input or output arguments, print the list of all functions with breakpoints and the line numbers where those breakpoints are set. If a function name func is specified then only report breakpoints for the named function.
The optional return argument brk_list is a struct array with the following fields.
The name of the function with a breakpoint.
The name of the m-file where the function code is located.
A line number, or vector of line numbers, with a breakpoint.
See also: dbclear, dbwhere.
Reusing the previous example,
dbstatus ("asind") will return
29. The breakpoints listed can then be cleared with the
Delete a breakpoint in the function func.
Function name as a string variable. When already in debug mode this argument should be omitted and only the line number should be given.
Line number from which to remove a breakpoint. Multiple lines may be given as separate arguments or as a vector.
When called without a line number specification all breakpoints in the named function are cleared.
If the requested line is not a breakpoint no action is performed.
See also: dbstop, dbstatus, dbwhere.
These functions can be used together to clear all the breakpoints in a particular function. For example:
dbclear ("asind", dbstatus ("asind"));
A breakpoint may also be set in a subfunction. For example, if a file contains the functions
function y = func1 (x) y = func2 (x); endfunction function y = func2 (x) y = x + 1; endfunction
then a breakpoint can be set at the start of the subfunction directly with
dbstop (["func1", filemarker(), "func2"]) ⇒ 5
filemarker returns a character that marks the
subfunctions from the file containing them.
Another simple way of setting a breakpoint in an Octave script is the
use of the
This function is normally used for simple debugging. When the
keyboard function is executed, Octave prints a prompt and waits
for user input. The input strings are then evaluated and the results
are printed. This makes it possible to examine the values of variables
within a function, and to assign new values if necessary. To leave the
prompt and return to normal execution type ‘return’ or ‘dbcont’.
keyboard function does not return an exit status.
keyboard is invoked without arguments, a default prompt of
‘debug> ’ is used.
See also: dbcont, dbquit.
keyboard function is typically placed in a script at the
point where the user desires that the execution be stopped. It
automatically sets the running script into the debug mode.