There are two additional support functions that allow the user to interrogate where in the execution of a script Octave entered the debug mode and to print the code in the script surrounding the point where Octave entered debug mode.
In debugging mode, report the current file and line number where execution is stopped.
When in debugging mode and called with no arguments, list the script file being debugged with line numbers. An optional range specification, specified as a string, can be used to list only a portion of the file.
When called with the name of a function, list that script file with line numbers.
You may also use
isdebugmode to determine whether the debugger is
Return true if in debugging mode, otherwise false.
Debug mode also allows single line stepping through a function using
In debugging mode, execute the next n lines of code. If n is omitted, execute the next single line of code. If the next line of code is itself defined in terms of an m-file remain in the existing function.
dbstep inwill cause execution of the next line to step into any m-files defined on the next line. Using
dbstep outwill cause execution to continue until the current function returns.
dbnextis an alias for