public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28480] pretty printing getting confused Date: Thu, 04 Nov 2021 18:07:46 +0000 [thread overview] Message-ID: <bug-28480-4717-5xWHdudOUe@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28480-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28480 --- Comment #16 from B. Larsen <blarsen at redhat dot com> --- Ah! I think I got it! GDB is using boffset to check if there is virtual inheritance. However, this test case has an empty struct, so the offset for both members is the same! If any members are added to struct S, GDB correctly identifies the ambiguity. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-04 18:07 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-20 22:43 [Bug gdb/28480] New: " jwakely.gcc at gmail dot com 2021-10-21 0:44 ` [Bug gdb/28480] " jwakely.gcc at gmail dot com 2021-10-21 0:49 ` jwakely.gcc at gmail dot com 2021-10-21 0:56 ` jwakely.gcc at gmail dot com 2021-10-21 3:23 ` simark at simark dot ca 2021-10-21 8:44 ` jwakely.gcc at gmail dot com 2021-10-26 19:14 ` blarsen at redhat dot com 2021-11-04 16:01 ` blarsen at redhat dot com 2021-11-04 16:52 ` jwakely.gcc at gmail dot com 2021-11-04 17:06 ` jwakely.gcc at gmail dot com 2021-11-04 17:09 ` jwakely.gcc at gmail dot com 2021-11-04 17:36 ` jwakely.gcc at gmail dot com 2021-11-04 17:42 ` jwakely.gcc at gmail dot com 2021-11-04 17:53 ` jwakely.gcc at gmail dot com 2021-11-04 17:56 ` simark at simark dot ca 2021-11-04 17:59 ` simark at simark dot ca 2021-11-04 18:07 ` blarsen at redhat dot com [this message] 2021-11-04 18:45 ` pedro at palves dot net 2021-11-04 19:40 ` blarsen at redhat dot com 2021-11-05 13:53 ` blarsen at redhat dot com 2021-11-05 14:29 ` [Bug c++/28480] Incorrect field ambiguity detection due to [[no_unique_address]] simark at simark dot ca 2021-11-25 12:56 ` cvs-commit at gcc dot gnu.org 2021-11-25 15:25 ` blarsen at redhat dot com 2021-12-11 7:49 ` cvs-commit 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-28480-4717-5xWHdudOUe@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).