public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/28908] New: Assertion `strstr (name, "::") == NULL' failed. listing member function names of a namespace class Date: Fri, 18 Feb 2022 21:53:20 +0000 [thread overview] Message-ID: <bug-28908-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28908 Bug ID: 28908 Summary: Assertion `strstr (name, "::") == NULL' failed. listing member function names of a namespace class Product: gdb Version: 11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: msebor at gmail dot com Target Milestone: --- I encountered the following internal error while testing the fix for pr28901. The error is with GNU gdb (GDB) Fedora 11.1-5.fc35 but it's reproducible with trunk. $ cat t.C && g++ -g3 t.C && gdb -batch -nx -ex "break main" -ex run -ex "print (N::A*)&b" -ex "list $1->N::A::f" a.out namespace N { struct A { void f () { } }; struct B: A { }; } N::B b; int main () { b.f (); } Breakpoint 1 at 0x40110a: file t.C, line 10. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Breakpoint 1, main () at t.C:10 10 b.f (); $1 = (N::A *) 0x40401d <b> ../../gdb/cp-namespace.c:178: internal-error: block_symbol cp_lookup_bare_symbol(const language_defn*, const char*, const block*, domain_enum, int): Assertion `strstr (name, "::") == 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] This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. ../../gdb/cp-namespace.c:178: internal-error: block_symbol cp_lookup_bare_symbol(const language_defn*, const char*, const block*, domain_enum, int): Assertion `strstr (name, "::") == 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] Aborted (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-02-18 21:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-18 21:53 msebor at gmail dot com [this message] 2022-02-18 21:54 ` [Bug c++/28908] " msebor at gmail dot com 2022-02-24 15:06 ` tromey at sourceware dot org 2023-12-30 15:45 ` ssbssa at sourceware dot org
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-28908-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).