because the IDE 2.0 supports live debugging I bought an Arduino Zero to debug my projects.
I am using IDE 2.0.3 and optimized for debugging.
I set a breakpoint and started debugging and hit the breakpoint - not bad.
BUT
the debugging is painfully slow - is this normal?
sometimes the debugger freezes and I have to restart the IDE
even when optimizing for debug the execution appears to skip some lines
I'm not quite sure how to reliably start debugging, sometimes it starts, sometimes not
Is this a IDE problem or a problem with my installation or just me?
Is there any official tutorial? I didn't find anything helpful yet.
Which specific part of the process (e.g., initialization, configuration, stepping) are you finding to be slow?
What are the exact symptoms of the freeze? Is the freeze limited to the debugger UI, or is the entire Arduino IDE interface unresponsive?
Have you been able to identify the specific conditions the freeze occurs under?
I have done quite a bit of testing of the debugger (though admittedly I have not had the opportunity to use it for the development of one of my own sketch projects). I was able to reproduce the known bugs reported by the users, but all the significant bugs were fixed recently when the Cortex-Debug VS Code extension used for the Arduino IDE debugger feature was updated.
The debugger section of the Arduino IDE issue tracker is looking pretty clean now:
Please provide a minimal demonstration sketch and instructions we can follow to reproduce the issue.
Does the skipping occur consistently, or is the skipping intermittent (i.e., changes in which lines are affected from one session or cycle to the next, lines skipped sometimes and reached other times)?
Please provide a detailed description of the procedure you are using to "start" the debugger.
There is some potential ambiguity when discussing this subject because there are two different operations that might be called "starting" the debugger:
Clicking the "Start Debugging" button on the Arduino IDE toolbar, which intiializes and starts the debugger.
Clicking the icon that looks like a play button (tooltip: "Start Debugging" in the DEBUG view, which starts the previously initialized debugger.
What is the specific symptoms you observe when it does not start?
I was not able to reproduce the problems you reported, but it might be only because I have not produced the same conditions you have. Things will likely become more clear once I have more information.
thanks for the reply! Obviously I missed the obvious place for the documentation - sorry
If tried debugging with the "Blink" example. This goes much smoother (maybe the serial output of my other sketch is responsible for the trouble?).
I still have difficulties to understand how to stop debugging and if I need to compile (verify) the sketch before debugging - I would have expected that pressing "Start Debugging" would trigger a compiler run if required.
Pressing STOP doesn't seem to have an effect and if I recompile and restart the number of threads increases (see screenshot).
