Condition in conditional breakpoint ignored: debugger stops there anyway

2 views (last 30 days)
It sometimes happens that conditions I set for a given breakpoint are ignored: the debugger will stop there even if the condition isn't yet met, as shown in the situation below, where no other breakpoints existed in the script:
Sometimes restarting Matlab seems to help, but not always. What is the reason for this?
Thanks for any help.
  3 Comments
z8080
z8080 on 20 May 2022
Just checked the same script (which needs complex debugging, with such conditional breakpoints) in R2022a, and the debugger follows the condition as normal - therefore it appears this is a bug in R2019b?!

Sign in to comment.

Answers (1)

Image Analyst
Image Analyst on 18 May 2022
Conditions are only updated, I believe, then the file is saved. If you change the condition you may have to save the file, which you might not be able to do if there are any changes that you've made while stopped at a break point.
  4 Comments
z8080
z8080 on 20 May 2022
Still seems worth ascertaining what doesn't work as expected in which version, does it not? Especially when it's about what I regard to be a rather essential feature, such as debugging.
Also, while I do have R2022a, I do go back to R2019b when I get tired of how slow R2022a runs on my system, and of the multiple new "features" such as the removal of overtype, etc

Sign in to comment.

Categories

Find more on Debugging and Analysis in Help Center and File Exchange

Products


Release

R2019b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!