octave: Call Stack
13.5 Call Stack
===============
The function being debugged may be the leaf node of a series of function
calls. After examining values in the current subroutine it may turn out
that the problem occurred in earlier pieces of code. Use ‘dbup’ and
‘dbdown’ to move up and down through the series of function calls to
locate where variables first took on the wrong values. ‘dbstack’ shows
the entire series of function calls and at what level debugging is
currently taking place.
-- : dbstack
-- : dbstack N
-- : dbstack -COMPLETENAMES
-- : [STACK, IDX] = dbstack (...)
Display or return current debugging function stack information.
With optional argument N, omit the N innermost stack frames.
Although accepted, the argument -COMPLETENAMES is silently ignored.
Octave always returns absolute filenames.
The arguments N and -COMPLETENAMES can be both specified in any
order.
The optional return argument STACK is a struct array with the
following fields:
file
The name of the m-file where the function code is located.
name
The name of the function with a breakpoint.
line
The line number of an active breakpoint.
column
The column number of the line where the breakpoint begins.
scope
Undocumented.
context
Undocumented.
The return argument IDX specifies which element of the STACK struct
array is currently active.
DONTPRINTYET See also: dbup XREFdbup, dbdown XREFdbdown, *noteDONTPRINTYET DONTPRINTYET See also: dbup XREFdbup, dbdown XREFdbdown,
dbwhere XREFdbwhere, dblist XREFdblist, *notedbstatus:
DONTPRINTYET DONTPRINTYET See also: dbup XREFdbup, dbdown XREFdbdown,
dbwhere XREFdbwhere, dblist XREFdblist, dbstatus
XREFdbstatus.
-- : dbup
-- : dbup N
In debugging mode, move up the execution stack N frames.
If N is omitted, move up one frame.
See also: dbstack XREFdbstack, dbdown XREFdbdown.
-- : dbdown
-- : dbdown N
In debugging mode, move down the execution stack N frames.
If N is omitted, move down one frame.
See also: dbstack XREFdbstack, dbup XREFdbup.