GDB crash

[martindusek]

Hi,

I have very hard times using debugging in Kinetis Design Studio 3.2.0

1) My breakpoint is never hit.

2) Sometimes when I set new breakpoint, GDB crashe. Crash log attached (pasting text (CTRL + V) doesn't work for me in this forum)

3) When some breakpoint is set when starting debugging, GDB also crashes.

How to fix it?

Original Attachment has been moved to: crash.txt.zip

[martindusek]

Is there anyone???? Please help me or tell me where can I get some help.

This is the log during GDB crash.

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/>.
Warning: the current language does not match this frame.
/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]
/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]
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

[BlackNight]

Hi Martin,

googling for the error message returns Failed to Debug with GDB: Breakpoints or Expressions on non-existing Locations | MCU on Eclipse 

So I think you have the problem described in that article: set a breakpoint on an address/function which does not exist.

Can you try clearing all breakpoints as outlined in that article to see if this helps?

Erich

[martindusek]

Hi Erich,

thanks for your response. Today I deleted my project and made it from scratch again and the problem disappeared.

I remember, that I had no breakpoints and still GDB crashed when I added new (first) breakpoint.

[BlackNight · Accepted solution]

Hi Martin,

I'm 99.9% sure it was the problem outlined with breakpoints on removed code. It happens as well once you have started the debug session and then you try to set a new (first) breakpoint on a function which has been removed.

Erich