Breakpoints unpredictable in R2011a
조회 수: 2(최근 30일)
표시 이전 댓글
Since upgrading to R2011a, breakpoints in my code are unpredictable. Sometimes they work, and sometimes they don't. My code worked fine with breakpoints in R2010b. I don't have any "clear all" statements, and the breakpoints are still visible as red dots in my code. The code I'm using is on the MATLAB path, and there is only one copy.
Anyone else having difficulty with breakpoints in this latest release? Even better, anyone know how to fix it?
댓글 수: 11
TB 2011년 9월 21일
The official word I got from The Mathworks is that it is fixed in R2011b, but no workaround for R2011a.
댓글 수: 6
Daniel Shub 2011년 9월 22일
While I am all for venting and in my opinion it is fine to vent here, nobody who can do anything is listening (not quite, but you get the idea). Go through the official channel of customer support to let them know how you feel.
Alexander Kosenkov 2011년 8월 31일
Extremely annoying bug, since R2011a. Breakpoints have their own lives, regardless of user actions. Just doesn't work.
As workaround, sometimes, it helps to modify file (add and remove space) and then saving it again. Otherwise I have to restart Matlab (obviously loosing all breakpoints). Clicking 'Clear all breakpoints in all files' and then setting breakpoints again - does not help for me.
Anyone here from Mathworks to comment?
댓글 수: 1
Andreas Goser 2011년 9월 22일
One user pointed me to this thread, as we were discussing aspects of the development timelines and fixing bugs. Indeed, MathWorks fixes bugs in the release under development and not by default for all affected older releases. But certainly, it is possible. And it happens. Please see the recent Service Pack releases. Those are responses on a number of (typically significant) bugs. In short, this is dependent on impact, frequeny and whether accpetable workarounds are available or not. I can just encourage you to describe the impact to Technical Support, so that they can provide this information to Development. You may think the impact is obvious? It is not.
댓글 수: 3
@Walter: Go to http://en.wikipedia.org/wiki/MATLAB and look for the "Release history". There are 2 SPs sincs 2006.
Lucas García 2011년 8월 31일
I haven't been able to reproduce this issue, but I have heard it from other users, so that makes it empirically a possible bug in R2011a. In any case, I will recommend that you report it to the Technical Support team mentioning your problem with as much detail as you can.
When you are debugging and type dbstatus, are the true breakpoint lines listed?
As a possible workaround, I will try the following:
>> feature accel off
>> feature jit off
댓글 수: 1
It cannot be called "workaround" to disable the JIT acceleration. Some of the loops will need 100 times more processing time, such that a program can become completely useless even if it only concerns the debugging.
Sean de Wolski 2011년 4월 21일
Are you calling it in cell mode by clicking "Evaluate Cell"?
댓글 수: 6
Adam 2012년 5월 2일
I didn't know this, maybe everyone else did...
The Matlab statement:
clears breakpoints. So if you have "clear all" in your script, any breakpoints after that line will be cleared before script execution reaches them, so Matlab won't break. Getting rid of this line was the solution in my case, but it may not work in every case.
[opinion] this functionality is DUMB and should be fixed. [/opinion]
댓글 수: 2
Find more on Debugging and Analysis in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!Start Hunting!