Weird behavior when debugging code invoked by timer

2 次查看（过去 30 天）
per isakson
per isakson 2013-3-4
编辑： per isakson 2019-2-22
This question is overtaken by Spurious fire from timer
.
This question is related to my question Debug code invoked by timer.
Am I the only one to experience the following weird behavior of Matlab?
I debug code that is invoked by a timer
  1. execution is halted by a break-point
  2. I do something interactively
  3. suddenly "a callback" is fired. Execution is still halted at the same break-point, but with a new workspace
  4. A new group of timercb, timercb and invoked_by_timer_catch is added to the stack drop-down-menu. See the screen clip below.
  5. R2012a 64bit
timer is not supposed to fire a new callback until the current callback is finished. Isn't that what the documentation says? I have seen it happen with "'TasksToExecute', 1".
Sorry the picture is so large.
  2 个评论
Jan
Jan 2013-3-4
Please show us how you define the TIMER such that we can try to reproduce the problem.
per isakson
per isakson 2013-3-4
编辑：per isakson 2013-3-6
Code relevant to this example is in the question that I link to in the first line. This happened (behavior showed) when I developed the code for the question linked to in this first line of this question.
However, I've seen this behavior since I started to use the timer a few years ago. I've never been able to understand (/reproduce) it.

请先登录，再进行评论。

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

回答（0 个）

类别

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

标签

Community Treasure Hunt

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

Start Hunting!

Translated by