Comments on: Useful Debugging Commands and Tips http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/ Loren Shure works on design of the MATLAB language at MathWorks. She writes here about once a week on MATLAB programming and related topics. Thu, 09 Feb 2012 04:19:21 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Loren Shure http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32877 Loren Shure Wed, 04 Jan 2012 13:59:20 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32877 Marcus- Glad this post helped you. --Loren Marcus-

Glad this post helped you.

–Loren

]]> By: Marcus http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32875 Marcus Wed, 04 Jan 2012 01:06:08 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32875 "breakpoints disappearing when debugging. This is often caused by a clear all in code being run." THANK YOU, this solved my problem. “breakpoints disappearing when debugging. This is often caused by a clear all in code being run.” THANK YOU, this solved my problem.

]]> By: Loren Shure http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32852 Loren Shure Fri, 16 Dec 2011 11:37:11 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32852 Brad- Sounds correct. Thanks. --Loren Brad-

Sounds correct. Thanks.

–Loren

]]> By: Brad Stiritz http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32849 Brad Stiritz Thu, 15 Dec 2011 20:07:00 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32849 Ben & Loren, >>Is there any command to *break to the debugger now* in a fashion that’s continuable? >I know of no way to do what you are requesting. What about the MATLAB function "keyboard"..? Doesn't this do exactly what Ben is asking for..? Brad Ben & Loren,

>>Is there any command to *break to the debugger now* in a fashion that’s continuable?

>I know of no way to do what you are requesting.

What about the MATLAB function “keyboard”..? Doesn’t this do exactly what Ben is asking for..?

Brad

]]> By: Loren http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32160 Loren Tue, 29 Mar 2011 21:33:14 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32160 Ben- I know of no way to do what you are requesting. --Loren Ben-

I know of no way to do what you are requesting.

–Loren

]]> By: Ben Voigt http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32159 Ben Voigt Tue, 29 Mar 2011 17:40:37 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-32159 Is there any command to *break to the debugger now* in a fashion that's continuable? Conditional breakpoints can get lost if the m-file gets moved or run on another computer, and calling error or a non-existent function breaks so I inspect variables but I can't then continue single-stepping. So I'd like something I can put into my scripts so when I detect no progress is being made, I can start single-stepping and find out why it's stuck. Is there any command to *break to the debugger now* in a fashion that’s continuable? Conditional breakpoints can get lost if the m-file gets moved or run on another computer, and calling error or a non-existent function breaks so I inspect variables but I can’t then continue single-stepping. So I’d like something I can put into my scripts so when I detect no progress is being made, I can start single-stepping and find out why it’s stuck.

]]> By: Loren http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-31107 Loren Thu, 25 Feb 2010 03:22:48 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-31107 Akiel- Please use the link to the right to make the suggestion to technical support. For what it's worth, I have tripped on this also. But landing in the editor to run more code is frequently handy. --Loren Akiel-

Please use the link to the right to make the suggestion to technical support. For what it’s worth, I have tripped on this also. But landing in the editor to run more code is frequently handy.

–Loren

]]> By: Akiel http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-31101 Akiel Wed, 24 Feb 2010 17:33:48 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-31101 Small thing - but I find somewhat annoying - don't know if there's a workaround, and maybe it's too much to hope for(?) for the default behaviour to be changed in the next version: When you set a breakpoint in your function and it gets called during execution, the cursor focus shifts to the m-file at the breakpoint, and half the time i end up typing into my m-file. Wouldn't it be better to focus the cursor at the K>> prompt when the breakpoint is reached? Small thing – but I find somewhat annoying – don’t know if there’s a workaround, and maybe it’s too much to hope for(?) for the default behaviour to be changed in the next version:

When you set a breakpoint in your function and it gets called during execution, the cursor focus shifts to the m-file at the breakpoint, and half the time i end up typing into my m-file. Wouldn’t it be better to focus the cursor at the K>> prompt when the breakpoint is reached?

]]> By: Loren http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-26107 Loren Mon, 11 Feb 2008 12:55:43 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-26107 Greg- I'm guessing you have a clear all somewhere in your code. That clears the debug state as well. If that's not the case, you probably should contact technical support for more help. --Loren Greg-

I’m guessing you have a clear all somewhere in your code. That clears the debug state as well. If that’s not the case, you probably should contact technical support for more help.

–Loren

]]> By: Greg http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-25993 Greg Sat, 09 Feb 2008 16:58:34 +0000 http://blogs.mathworks.com/loren/2007/12/07/useful-debugging-commands-and-tips/#comment-25993 Matlab used to stop on error, and at the command line level it still does, but for some reason it changed, and now if I insert a bad line of code into an m-file that is deep in the program, the error appears to simply pop the stack and continue, rather than stopping. To find an error, I am reduced to stepping through the program to see where it fails to go the next instruction. At the command line, I get >> dbstatus Stop if error. but it doesn't do it. This started when I tried out 'stop if caught error' etc., but now I cannot get back to the original state, much to my regret. What is happening? Thanks - Matlab used to stop on error, and at the command line level it still does, but for some reason it changed, and now if I insert a bad line of code into an m-file that is deep in the program, the error appears to simply pop the stack and continue, rather than stopping. To find an error, I am reduced to stepping through the program to see where it fails to go the next instruction. At the command line, I get

>> dbstatus

Stop if error.

but it doesn’t do it. This started when I tried out ‘stop if caught error’ etc., but now I cannot get back to the original state, much to my regret. What is happening?

Thanks -

]]>