MATLAB Basics: Using dbstop if error

When MATLAB throws an error, if you are in a function, you will end up at the base workspace and lose access to the variables as they were in the function when the error was thrown. This makes it difficult to understand why the error occurred.

With the debugger, MATLAB can stop when the error is thrown, so the variables are still in scope. This makes debugging much easier.

Video Content

You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

2 Responses to “MATLAB Basics: Using dbstop if error”

Eric S replied on August 28th, 2008 at 11:37 am :

It would be great to stop the debugger from coughing somewhere inside the more “internal” functions.
Is there a way to specify not to barf in certain directories, or in the ones you’re developing in only?

Cheers,

Eric

Scott Hirsch replied on August 28th, 2008 at 12:42 pm :

Eric -

That’s a nice suggestion. I often get frustrated when debugging GUIDE guis and ending up inside of guimainfcn. I can’t think of a direct way to handle this - there might be some games you could do with stopping based on certain error IDs, but I’m not sure how far this would get you.

- scott

About

Doug Hull is an Application Engineer at The MathWorks. A MATLAB user since 1994, he gets paid to live, eat, and breathe MATLAB! This blog is dedicated to promoting the File Exchange by highlighting files and original video content.

Doug’s Pick of the Week

April 28th, 2008