Debug Mode - GNU Octave
Description: GNU Octave

Next: Call Stack, Previous: Breakpoints, Up: Debugging

### 13.4 Debug Mode

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.

— Loadable Function: dbwhere ()

> Show where we are in the code

> See also: dbclear, dbstatus, dbstop.

— Loadable Function: dbtype ()

> List script file with line numbers.

> See also: dbclear, dbstatus, dbstop.

You may also use `isdebugmode` to determine whether the debugger is currently active.

— Loadable Function: isdebugmode ()

> Return true if debug mode is on, otherwise false.

> See also: dbstack, dbclear, dbstop, dbstatus.

Debug mode also allows single line stepping through a function using the commands `dbstep`.

— Command: dbstep
— Command: dbstep n
— Command: dbstep in
— Command: dbstep out

> 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.

> Using `dbstep in` will cause execution of the next line to step into any m-files defined on the next line. Using `dbstep out` will cause execution to continue until the current function returns.

> See also: dbcont, dbquit.