Condition in conditional breakpoint ignored: debugger stops there anyway

8 次查看（过去 30 天）
z8080
z8080 2022-5-18
评论： z8080 2022-5-20
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 个评论
显示 1更早的评论
z8080
z8080 2022-5-20
Thanks Matt - indeed, I know the Workspace sometimes doesn't properly update the variable contents, but in this case the value of the variable has indeed been verified at the command prompt
z8080
z8080 2022-5-20
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?!

请先登录，再进行评论。

请先登录，再回答此问题。

回答（1 个）

Image Analyst
Image Analyst 2022-5-18
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 个评论
显示 2更早的评论
Image Analyst
Image Analyst 2022-5-20
Perhaps, but the good news is that they fixed it and you have R2022a so you're all set. 🙂
z8080
z8080 2022-5-20
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

请先登录，再进行评论。

类别

在 Help Center 和 File Exchange 中查找有关 Whos 的更多信息

标签

产品


版本

R2019b

Community Treasure Hunt

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

Start Hunting!

Translated by