public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31281] [gdb] intrusive_list.h:329: internal-error: push_back: Assertion elem_node->prev == INTRUSIVE_LIST_UNLINKED_VALUE failed. Date: Wed, 24 Jan 2024 19:23:28 +0000 [thread overview] Message-ID: <bug-31281-4717-W9NgZMIQJ0@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31281-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31281 Simon Marchi <simark at simark dot ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simark at simark dot ca --- Comment #6 from Simon Marchi <simark at simark dot ca> --- I bisected gcc, the failure appeared with this commit: c++: non-dependent .* operand folding [PR112427] https://gitlab.com/gnutools/gcc/-/commit/d3f48f68227 I know nothing about compilers, so I don't know what the code changes. But the included test case uses a pointer-to-member, which is somewhat relevant in our case. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-24 19:23 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-23 17:59 [Bug gdb/31281] New: [gdb] intrusive_list.h:329: internal-error: push_back: Assertion elem_node->prev == INTRUSIVE_LIST_UNLIKED_VALUE failed blarsen at redhat dot com 2024-01-24 15:00 ` [Bug gdb/31281] " sam at gentoo dot org 2024-01-24 15:00 ` sam at gentoo dot org 2024-01-24 15:05 ` blarsen at redhat dot com 2024-01-24 16:17 ` tromey at sourceware dot org 2024-01-24 16:37 ` ssbssa at sourceware dot org 2024-01-24 16:38 ` [Bug gdb/31281] [gdb] intrusive_list.h:329: internal-error: push_back: Assertion elem_node->prev == INTRUSIVE_LIST_UNLINKED_VALUE failed vries at gcc dot gnu.org 2024-01-24 17:06 ` vries at gcc dot gnu.org 2024-01-24 17:18 ` simark at simark dot ca 2024-01-24 18:11 ` blarsen at redhat dot com 2024-01-24 19:23 ` simark at simark dot ca [this message] 2024-01-24 19:24 ` vries at gcc dot gnu.org 2024-01-24 19:41 ` vries at gcc dot gnu.org 2024-01-24 21:02 ` simark at simark dot ca 2024-01-24 22:01 ` vries at gcc dot gnu.org 2024-01-24 22:39 ` vries at gcc dot gnu.org 2024-01-25 3:51 ` simon.marchi at polymtl dot ca 2024-01-25 8:45 ` vries at gcc dot gnu.org 2024-01-25 12:38 ` simon.marchi at polymtl dot ca 2024-01-25 14:04 ` [Bug build/31281] " vries at gcc dot gnu.org 2024-01-25 14:21 ` vries at gcc dot gnu.org 2024-01-25 15:30 ` cvs-commit at gcc dot gnu.org 2024-01-25 15:31 ` vries at gcc dot gnu.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-31281-4717-W9NgZMIQJ0@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).