A problem internal to GDB has been detected

Discussions concerning TrueSTUDIO for STM32 9.0.0 and later versions.

Moderators: Markus Girdland, Mattias Norlander

Oleg
Posts: 1
Joined: Sun Dec 16, 2018 3:21 pm

A problem internal to GDB has been detected

Postby Oleg » Sun Dec 16, 2018 3:27 pm

Hello guys.
I have a problem with the debugger. When I try to start the debugger, it crashes with an error.

This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

/home/build/gcc-arm-none-eabi-6-2017-q1-update/src/gdb/gdb/cp-namespace.c:343: internal-error: cp_search_static_and_baseclasses: Assertion `name[prefix_len + 1] == ':'' 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/gcc-arm-none-eabi-6-2017-q1-update/src/gdb/gdb/cp-namespace.c:343: internal-error: cp_search_static_and_baseclasses: Assertion `name[prefix_len + 1] == ':'' 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]

angsuarez
Posts: 1
Joined: Sun Dec 23, 2018 6:52 pm

Re: A problem internal to GDB has been detected

Postby angsuarez » Sun Dec 23, 2018 7:21 pm

Hello

I have the same problem: GDB server internal error with similar text to previous message.


The sequence on console :

Waiting for debugger connection...
Debugger connected
Encountered a Socket Error, Exiting..
Debugger connection lost.
Shutting down...

O.S. is Win 10 with McAfee 's firewall.

The firmware is loaded in the target (stm32f103) and I can run de program using "ST link utility", and see messages on the SW0 console.

Thanks

JulienD
Posts: 9
Joined: Mon Nov 19, 2018 10:20 am

Re: A problem internal to GDB has been detected

Postby JulienD » Mon Jan 07, 2019 1:28 pm

Hello,

Same here.


/home/build/gcc-arm-none-eabi-6-2017-q1-update/src/gdb/gdb/cp-namespace.c:343: internal-error: cp_search_static_and_baseclasses: Assertion `name[prefix_len + 1] == ':'' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session?
This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.


TS 9.2.0
on stm32F429VE
with segger jtrace pro.
win 7 64.

This project with this board and this probe worked "before".


Any help would be greatly appreciated.

Best regards
Julien

JulienD
Posts: 9
Joined: Mon Nov 19, 2018 10:20 am

Re: A problem internal to GDB has been detected

Postby JulienD » Mon Jan 07, 2019 1:37 pm

OK, from here : https://stackoverflow.com/questions/378 ... aseclasses

I had a similar problem in Eclipse with GDB crashing. I had some old breakpoints active in the eclipse workspace. After removal of these breakpoints from other projects the issue was resolved.


Sometimes world is cruel...


Return to “TrueSTUDIO for STM32 discussions”

Who is online

Users browsing this forum: No registered users and 3 guests