GNU Octave Manual Version 3 by John W. Eaton, David Bateman, Søren Hauberg Paperback (6"x9"), 568 pages ISBN 095461206X RRP £24.95 ($39.95) Get a printed copy>>>

GNU Octave Manual Version 3 Buy the book here >>> support free software

13.1 Entering Debug Mode

There are two basic means of interrupting the execution of an Octave script. These are breakpoints see section 13.2 Breakpoints, discussed in the next section and interruption based on some condition.

Octave supports three functions which control the conditions for entering debug mode, debug_on_interrupt, debug_on_warning and debug_on_error.

Built-in Function: val = debug_on_interrupt ()

Built-in Function: old_val = debug_on_interrupt (new_val)

Query or set the internal variable that controls whether Octave will try to enter debugging mode when it receives an interrupt signal (typically generated with C-c). If a second interrupt signal is received before reaching the debugging mode, a normal interrupt will occur.

Built-in Function: val = debug_on_warning ()

Built-in Function: old_val = debug_on_warning (new_val)

Query or set the internal variable that controls whether Octave will try to enter the debugger when a warning is encountered.

Built-in Function: val = debug_on_error ()

Built-in Function: old_val = debug_on_error (new_val)

Query or set the internal variable that controls whether Octave will try to enter the debugger when an error is encountered. This will also inhibit printing of the normal traceback message (you will only see the top-level error message).