Folks,
I am unable to use the Segger Jlink V9.3 to debug my embedded C code. I am able to program my MCU but when it tries to debug the Jlink crashes and MCU does not get properly restarted. I have tried two different J-links and both fail. I have used this setup for years and have not experienced this problem before. I even tried to back out the recent code that I added but the problem persists. I have been doing updates on this particular PCB for more than 4 days without any trouble. I do not have another board to try, no.
Any ideas what is happening? The Segger JLink debugger is a key piece of equipment in my development toolkit.
Thank you.
Phil
----
Here is the console error I am seeing:
Display All
I am unable to use the Segger Jlink V9.3 to debug my embedded C code. I am able to program my MCU but when it tries to debug the Jlink crashes and MCU does not get properly restarted. I have tried two different J-links and both fail. I have used this setup for years and have not experienced this problem before. I even tried to back out the recent code that I added but the problem persists. I have been doing updates on this particular PCB for more than 4 days without any trouble. I do not have another board to try, no.
Any ideas what is happening? The Segger JLink debugger is a key piece of equipment in my development toolkit.
Thank you.
Phil
----
Here is the console error I am seeing:
Source Code
- A problem internal to GDB has been detected,
- further debugging may prove unreliable.
- Quit this debugging session? (y or n) [answered Y; input not from terminal]
- /home/build/work/GCC-4-8-build/src/gdb/gdb/linespec.c:2445: internal-error: decode_line_full: Assertion `state->canonical_names[i].suffix != NULL' failed.
- A problem internal to GDB has been detected,
- further debugging may prove unreliable.
- Create a core file of GDB? (y or n) [answered Y; input not from terminal]