public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "phil.rados at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/27043] New: The gdb debugger can't read symbols from a (g++-10 compiled) c++ file. Date: Wed, 09 Dec 2020 16:31:38 +0000 [thread overview] Message-ID: <bug-27043-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27043 Bug ID: 27043 Summary: The gdb debugger can't read symbols from a (g++-10 compiled) c++ file. Product: gdb Version: 10.1 Status: UNCONFIRMED Severity: critical Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: phil.rados at gmail dot com Target Milestone: --- Created attachment 13031 --> https://sourceware.org/bugzilla/attachment.cgi?id=13031&action=edit 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 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-12-09 16:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-09 16:31 phil.rados at gmail dot com [this message] 2020-12-14 19:04 ` [Bug c++/27043] " simark at simark dot ca 2020-12-14 19:05 ` simark at simark dot ca 2021-01-05 13:08 ` nasrmaher1 at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-27043-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).