Bug 27043 - The gdb debugger can't read symbols from a (g++-10 compiled) c++ file.
Summary: The gdb debugger can't read symbols from a (g++-10 compiled) c++ file.
Status: RESOLVED DUPLICATE of bug 26912
Alias: None
Product: gdb
Classification: Unclassified
Component: c++ (show other bugs)
Version: 10.1
: P2 critical
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-09 16:31 UTC by phil.rados
Modified: 2021-01-05 13:08 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments
This is how the bug is replicated (703.77 KB, image/png)
2020-12-09 16:31 UTC, phil.rados
Details

Note You need to log in before you can comment on or make changes to this bug.
Description phil.rados 2020-12-09 16:31:38 UTC
Created attachment 13031 [details]
This is how the bug is  replicated

../../gdb/thread.c:95: internal-error: struct thread_info *inferior_thread(): Assertion `current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

This is the basic Error message. The detailed version is in the attachment.
It seems like it cannot read the symbols from the compiled main.cpp file.

If you have an answer you can maybe answer my StackOverflow question:
https://stackoverflow.com/questions/65187983/my-gdb-debugger-isnt-responding-when-i-launch-it?noredirect=1#comment115277766_65187983
Comment 1 Simon Marchi 2020-12-14 19:04:15 UTC
I think this is a duplicate of 26761.

Note there hasn't been significant contributions to GDB for macOS for a while, so we would need some manpower (or womenpower) to fix these bugs.

*** This bug has been marked as a duplicate of bug 26761 ***
Comment 2 Simon Marchi 2020-12-14 19:05:32 UTC
Sorry, wrong bug number, it's 26912.

*** This bug has been marked as a duplicate of bug 26912 ***
Comment 3 Maher 2021-01-05 13:08:40 UTC
Hi
I have the same problem as you. Did you get any solution ?