debug.cc File Reference

#include <deque>
#include <fstream>
#include <iomanip>
#include <iostream>
#include <limits>
#include <set>
#include <string>
#include "dNDArray.h"
#include "bp-table.h"
#include "call-stack.h"
#include "defun.h"
#include "error.h"
#include "errwarn.h"
#include "file-ops.h"
#include "help.h"
#include "input.h"
#include "interpreter-private.h"
#include "interpreter.h"
#include "octave-preserve-stream-state.h"
#include "ov-usr-fcn.h"
#include "ov.h"
#include "ovl.h"
#include "pager.h"
#include "parse.h"
#include "pt-eval.h"
#include "unwind-prot.h"
#include "utils.h"
#include "variables.h"

Include dependency graph for debug.cc:

Go to the source code of this file.

Functions
when function syntax is the lines may also be passed as a single vector	argument (ode{[ar{line1}, ar{line2}, ots{}]}). ar
is any Octave expression that can be evaluated in the code context that exists at the breakpoint When the breakpoint is and execution will stop if for example because it refers to an undefined an error will be thrown Expressions with side	effects (such as ode{y++> 1}) will alter variables
OCTAVE_EXPORT octave_value_list	Fdbstop (const octave_value_list &args, int) If ile
static octave_value	intmap_to_ov (const octave::bp_table::intmap &line)

Variables
is any Octave expression that can be evaluated in the code context that exists at the breakpoint When the breakpoint is	ar {condition} will be evaluated
is any Octave expression that can be evaluated in the code context that exists at the breakpoint When the breakpoint is	encountered
has a subfunction then a breakpoint in it defaults to the first executable line in the file	ile {func.m}. Multiple lines can be specified in a single command
has a subfunction	ode {func2}
when function syntax is	used
is any Octave expression that can be evaluated in the code context that exists at the breakpoint When the breakpoint is and execution will stop if for example because it refers to an undefined	variable

Function Documentation

argument()

when function syntax is the lines may also be passed as a single vector argument

(

ode{[ar{line1}, ar{line2}, ots{}]}

)

Definition at line 171 of file debug.cc.

effects()

is any Octave expression that can be evaluated in the code context that exists at the breakpoint When the breakpoint is and execution will stop if for example because it refers to an undefined an error will be thrown Expressions with side effects

(

such as ode{y++> 1}

)

Fdbstop()

OCTAVE_EXPORT octave_value_list Fdbstop	(	const octave_value_list &	args,
		int
	)

Definition at line 171 of file debug.cc.

intmap_to_ov()

static octave_value intmap_to_ov ( const octave::bp_table::intmap &  line )

static

Definition at line 61 of file debug.cc.

References i, p, octave_value::resize(), and retval.

Variable Documentation

ar

is any Octave expression that can be evaluated in the code context that exists at the breakpoint When the breakpoint is and execution will stop if ar {condition} will be evaluated

Definition at line 171 of file debug.cc.

encountered

is any Octave expression that can be evaluated in the code context that exists at the breakpoint When the breakpoint is encountered

Definition at line 171 of file debug.cc.

ile

has a subfunction then a breakpoint in it defaults to the first executable line in the file ile {func.m}. Multiple lines can be specified in a single command

Definition at line 171 of file debug.cc.

ode

has a subfunction then a breakpoint in ode {func2}

Definition at line 171 of file debug.cc.

used

when function syntax is used

Definition at line 171 of file debug.cc.

Referenced by octave::delimited_stream::getline().

variable

is any Octave expression that can be evaluated in the code context that exists at the breakpoint When the breakpoint is and execution will stop if for example because it refers to an undefined variable

Definition at line 171 of file debug.cc.