Path: news.mathworks.com!not-for-mail
From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Error lands in debugger instead?
Date: Tue, 9 Oct 2007 13:59:22 +0000 (UTC)
Organization: Yale University School of Medicine
Lines: 8
Message-ID: <feg1fq$ptf$1@fred.mathworks.com>
Reply-To: <HIDDEN>
NNTP-Posting-Host: webapp-02-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1191938362 26543 172.30.248.37 (9 Oct 2007 13:59:22 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Tue, 9 Oct 2007 13:59:22 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 5904
Xref: news.mathworks.com comp.soft-sys.matlab:432003



Is there a better way to debug code?  I run my program, and it halts with an 
error.  Then I click on the error statement, go to the editor, set a breakpoint, 
and run the program again, this time to halt it so I can look at the variables.

Why can't a fatal error put me directly into the debugger, as if the program 
encountered a breakpoint?  Then I could select which stack frame I wanted, and 
look at the variables directly.