### 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 ()

> In debugging mode, report the current file and line number where execution is stopped.

> See also: dbstatus, dbcont, dbstep, dbup.

— Loadable Function: dbtype ()
— Loadable Function: dbtype ("startl:endl")
— Loadable Function: dbtype ("func")
— Loadable Function: dbtype ("func", "startl:endl")

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

> See also: dbstatus, dbstop.

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

— Loadable Function: isdebugmode ()

> Return true if in debugging mode, otherwise false.

> See also: dbwhere, dbstack, 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
— Command: dbnext ...

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

> `dbnext` is an alias for `dbstep`.

> See also: dbcont, dbquit.