debug
-- execute a procedure in
single-step modedebug(
statement)
starts the MuPAD
debugger, allowing to execute statement
step by step.
debug(statement)
statement |
- | any MuPAD object; typically a function call |
the return value of statement
.
noDebug
, Pref::ignoreNoDebug
,
prog::check
, prog::profile
, prog::trace
debug
switches the state of the MuPAD kernel to
debug mode and, if statement
contains procedure calls that can be debugged, enters the
interactive MuPAD debugger for controlled single-step execution
of statement
.The debugger features single stepping, inspection of variables and stack frames, breakpoints, etc. Read the online help of the debugger window for a description.
After calling Pref::ignoreNoDebug(TRUE)
, the
procedure option noDebug is ignored.
debug(
statement)
returns the same result
as statement
, if the execution is not aborted within the
debugger by the user.debug
is a function of the system kernel.We start the debugger for stepwise execution of the
statement int(cos(x),x)
,
which integrates the cosine function:
>> debug(int(cos(x), x)):
Since this also applies to procedures that were read before debug mode was switched on, it is recommended to start the kernel in debug mode (see below) when bigger applications are to be debugged.
debug
. It remains
activated until the end of the session.
It is possible to start the kernel in debug mode. On Windows platforms, this can be configured by choosing ``Options'' in the ``View'' menu and then clicking on ``Kernel''. In the graphical user interface on UNIX systems, clicking on ``Kernel Debug Mode'' in the ``Options'' menu toggles this setting. On a Macintosh, choose ``Preferences'' from the ``File'' menu and then ``Kernel''.