CODEWITHSUNDEEP
matlabdebuggingif-statementtry-catch
Mazza
Mazza

Reputation: 71

Matlab: Turning try/catch on and off for debugging

I am using a try-catch statement for a lengthy calcuation similar to the following:

for i=1:1000
    try 
        %do a lot of stuff
    catch me
        sendmail('[email protected]', 'Error in Matlab', parse_to_string(me));
    end
end

When I am writing on my code I do not want to jump in the catch statement because I like Matlabs dbstop if error feature. I know it is possible to use dbstop if all error in order to avoid jumping in the catch statement (I found that here: http://www.mathworks.com/matlabcentral/newsreader/view_thread/102907 .)

But the problem is that Matlab has a lot of inbuilt functions which throw errors which are caught and handled by other inbuilt functions. I only want to stop at errors caused by me.

My approach would be to use some statement similar to 

global debugging; % set from outside my function as global variable
for i=1:1000
    if  ~debugging 
        try 
    end

        %do a lot of stuff

    if  ~debugging
        catch me
            sendmail('[email protected]', 'Error in Matlab', parse_to_string(me));
        end
    end 
end

This does not work because Matlab doesn't see that try and catch belong to each other.

Are there any better approaches to handle try/catch statements when debugging? I have been commenting in and out the try/catch, but that is pretty annoying and cumbersome.

Upvotes: 6

Views: 1235

Answers (3)

M.Hossein Rahimi
M.Hossein Rahimi

Reputation: 617

As you can see in the Matlab documentation, dbclear all removes all breakpoints in all MATLAB® code files, and all breakpoints set for errors, caught errors, caught error identifiers, warnings, warning identifiers, and naninf.

If you need to remove all the breakpoints in a certain file you can use dbclear in mFilePath and you can always use dbstatus to check the current setup.

And as @dennis-jaheruddin mentioned, dbstop if caught error could be used for run-time error that occurs within the try portion of a try/catch block. If you want to clear a breakpoint set for a specific error, then specify the message id.

Upvotes: 0

Dennis Jaheruddin
Dennis Jaheruddin

Reputation: 21563

The solution that you are looking for is dbstop if caught error.

Before I found that, debugging code with try catch blocks always drove me crazy.

Upvotes: 5

Daniel
Daniel

Reputation: 36710

for i=1:1000
    try 
        %do a lot of stuff
    catch me
        if ~debugging
             sendmail('[email protected]', 'Error in Matlab', parse_to_string(me));
        else
             rethrow(me)
        end
    end
end

This code should match your requirements.

Upvotes: 1

Related Questions