Internal GDB failure and crash for breakpoint without code

[Erich Styger]

I'm facing GDB crashers with launching gdb with breakpoints for code which is not available.
Release used: v4.8 q2 and as well v4.8 q3 (standard releases from launchpad) with Eclipse.

I have described the problem in details (with workaround) here: http://mcuoneclipse.com/2014/10/11/failed-to-debug-with-gdb-breakpoints-or-expressions-on-non-existing-locations/

The target endianness is set automatically (currently little endian)
/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.

Erich

[Terry Guo (terry.guo)]

Hi Erich,

Thanks for reporting. Is it possible for you to export your Eclipse-based project to a Makefile-based project for me to reproduce? I don't have Eclipse at hand. Thanks very much.

[Terry Guo (terry.guo)]

Would you please provide your final image for us to reproduce?

[Erich Styger (erich-styger)]

Hi Terry,
I appologize that it took me so long to respond to this issue.
The good news is: I tried to reproduce this issue with the v4.9q4_2014 release which just came out a few days ago.
And the problem is fixed in that gdb version :-)
So this issue can be closed.

For completeness, I have attached my test project (for the Freescale KL25Z).

Many thanks,
Erich