Weird behavior when debugging code invoked by timer
1 view (last 30 days)
Show older comments
.
Am I the only one to experience the following weird behavior of Matlab?
I debug code that is invoked by a timer
- execution is halted by a break-point
- I do something interactively
- suddenly "a callback" is fired. Execution is still halted at the same break-point, but with a new workspace
- A new group of timercb, timercb and invoked_by_timer_catch is added to the stack drop-down-menu. See the screen clip below.
- 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 Comments
Jan
on 4 Mar 2013
Please show us how you define the TIMER such that we can try to reproduce the problem.
Answers (0)
See Also
Categories
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!