Open zougloub opened 1 year ago
Thanks for the report. It's highly likely that the step commands have differences between pyOCD and OpenOCD that gdb is somehow unhappy with, whether or not it's technically a bug.
Do you have a project that you can provide that reproduces it? There's a good chance it's specific to the code being debugged. In any case, I'll try to reproduce it as soon as I get a chance.
A couple other questions for you.
What MCU and CPU? Are you using an RTOS and pyOCD's RTOS support?
Hi,
I have used the same GDB macro in OpenOCD and pyOCD and in pyOCD it fails with an internal gdb error. I don't know how reproducible my scenario is, but I have a target device that is repetitively calling a function and I had a breakpoint that was printing arguments and continuing execution.
After some cycles (~ 20) gdb would fail with:
There are open bugs in GDB for this messages (eg. this one) but since the problem is not happening with OpenOCD I'm opening an issue here.