public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jengelh at inai dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/25894] New: gdb crash on uncanny command Date: Wed, 29 Apr 2020 10:15:58 +0000 [thread overview] Message-ID: <bug-25894-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=25894 Bug ID: 25894 Summary: gdb crash on uncanny command Product: gdb Version: 8.3.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: jengelh at inai dot de Target Milestone: --- » cat x.cpp struct T { int v; }; int main() { T t, *u = &t; u->T::v = 2; return u->T::v; } » g++ x.cpp -ggdb3 » gdb a.out GNU gdb (GDB; openSUSE Tumbleweed) 8.3.1 (gdb) b main Breakpoint 1 at 0x1129: file x.cpp, line 4. (gdb) r Starting program: /dev/shm/a.out Breakpoint 1, main () at x.cpp:4 4 T t, *u = &t; (gdb) n 5 u->T::v = 2; (gdb) 6 return u->T::v; (gdb) l u->T::v ../../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) A nonsensical command should not crash gdb. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-04-29 10:15 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-29 10:15 jengelh at inai dot de [this message] 2020-08-09 15:02 ` [Bug c++/25894] " tromey at sourceware dot org 2023-12-30 13:06 ` ssbssa at sourceware dot org 2023-12-30 13:07 ` ssbssa 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-25894-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).