MATLAB Function Reference Volume 1: A - E - Bad Request

dbstop
2-390
subfun. You can then use the debugging utilities, review the workspace, or
issue any valid MATLAB function. Use dbcont or dbstep to resume execution
of mfile. Use dbquit to exit from the Debugger.
dbstop if error stops execution when any M-file you subsequently run
produces a run-time error, putting MATLAB in debug mode, paused at the line
that generated the error. The M-file must be in a directory that is on the search
path or in the current directory. It does not include run-time errors that are
detected within a try...catch block. You cannot resume execution after an
error. Use dbquit to exit from the Debugger.
dbstop if all error is the same as dbstop if error, except that it stops
execution on any type of run-time error, including errors that are detected
within a try...catch block.
dbstop if warning stops execution when any M-file you subsequently run
produces a run-time warning, putting MATLAB in debug mode, paused at the
line that generated the warning. The M-file must be in a directory that is on
the search path or in the current directory. Use dbcont or dbstep to resume
execution.
dbstop if naninf stops execution when any M-file you subsequently run
encounters an infinite value (Inf), putting MATLAB in debug mode, paused at
the line where Inf was encountered. The M-file must be in a directory that is
on the search path or in the current directory. Use dbcont or dbstep to resume
execution. Use dbquit to exit from the Debugger.
dbstop if infnan stops execution when any M-file you subsequently run
encounters a value that is not a number (NaN), putting MATLAB in debug
mode, paused at the line where NaN was encountered. The M-file must be in a
directory that is on the search path or in the current directory. Use dbcont or
dbstep to resume execution. Use dbquit to exit from the Debugger.
Remarks The at, in, and if keywords, familiar to users of the UNIX debugger dbx, are
optional.