arm-none-eabi-gdb.exe has stopped working

cancel
Showing results for 
Search instead for 
Did you mean: 

arm-none-eabi-gdb.exe has stopped working

682 Views
Contributor III

I get this error quite often with both a PE Multilink and Segger J-trace.

Trying to debug a K22.  Using latest KDS and Processor Expert.

Running bare metal.  No dynamic memory.  

It started when I add additional functions to my main loop.

Any ideas?  Do I need to alter the project properties?

pastedImage_1.png

Labels (1)
Tags (3)
0 Kudos
3 Replies

46 Views
Contributor III

UPDATE:  I am using GIT (bitbucket with sourcetree).  Once I move the project outside the GIT environment, it started working.  Has anyone seen this problem before?

Some more info.

Error occurs after erasing and programming the flash memory.

Here is the terminal printout:

GNU gdb (GNU Tools for ARM Embedded Processors) 7.6.0.20140731-cvs
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
monitor preserve0 0
monitor selectcore 0
/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.
Quit this debugging session? (y or n) [answered Y; input not from terminal]

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
/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]

0 Kudos

46 Views
NXP Employee
NXP Employee

Your problem is the one described here: Failed to Debug with GDB: Breakpoints or Expressions on non-existing Locations | MCU on Eclipse 

(remove all breakpoints to fix it).

I hope this helps,

Erich

0 Kudos

46 Views
Contributor III

Works, but only if you remove the breakpoint (as mentioned in the link

below).

Thanks for the help!

Brad

0 Kudos