List all breakpoints


dbstatus file
s = dbstatus(...)


dbstatus lists all the breakpoints in effect including errors, caught errors, warnings, and naninfs.

dbstatus file displays a list of the line numbers for which breakpoints are set in the specified file, where file is a MATLAB® code file function name or a MATLAB relative partial path. Each line number is a hyperlink you can click to go directly to that line in the Editor.

dbstatus('-completenames') displays, for each breakpoint, the absolute file name and the sequence of functions that nest the function containing the breakpoint.

s = dbstatus(...) returns breakpoint information in an m-by-1 structure with the fields listed in the following table. Use this syntax to save breakpoint status and restore it at a later time using dbstop(s)—see dbstop for an example.


Function name.


Full path for file containing breakpoints.


Vector of breakpoint line numbers.


Vector of integers representing the anonymous functions in the line field. For example, 2 means the second anonymous function in that line. A value of 0 means the breakpoint is at the start of the line, not in an anonymous function.


Cell vector of breakpoint conditional expression strings corresponding to lines in the line field.


Condition string ('error', 'caught error', 'warning', or 'naninf').


When cond is 'error', 'caught error', or 'warning', a cell vector of MATLAB message identifier strings for which the particular cond state is set.

Use dbstatus class/function, dbstatus private/function, or dbstatus class/private/function to determine the status for methods, private functions, or private methods (for a class named class).

In all forms you can further qualify the function name with a local function name, as in dbstatus function>localfunction.

More About

expand all


In the syntax, file can be a file, or the path to a function within a file. For example

Breakpoint for foo>myfun is on line 9

means there is a breakpoint at the myfun local function, which is line 9 in the file foo.m.

Introduced before R2006a

Was this topic helpful?