public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/29243] New: infinite loop in generic_value_print Date: Fri, 10 Jun 2022 23:46:46 +0000 [thread overview] Message-ID: <bug-29243-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29243 Bug ID: 29243 Summary: infinite loop in generic_value_print Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: roland at gnu dot org Target Milestone: --- Created attachment 14142 --> https://sourceware.org/bugzilla/attachment.cgi?id=14142&action=edit x86_64-linux-gnu target assembly source The source to reproduce this is quite small. However, GCC 12 does not emit DWARF that causes the issue in GDB. Current ToT Clang does. I've attached the .s file produced by Clang; turning that into an object that you can load into gdb should reproduce the same problem. ``` // clang++ -std=c++17 -O2 -g3 -gdwarf-5 -shared -o foo.so foo.cc // gdb foo.so // (gdb) i func struct S { bool x, y; }; namespace { template <auto M> constexpr bool kFoo = true; } // bool t() { return kFoo<&S::x>; } bool f() { return kFoo<&S::y>; } ``` -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-06-10 23:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-10 23:46 roland at gnu dot org [this message] 2022-06-10 23:48 ` [Bug c++/29243] " roland at gnu dot org 2022-06-11 19:38 ` tromey at sourceware dot org 2022-06-13 19:39 ` roland at gnu dot org 2022-06-13 19:42 ` roland at gnu dot org 2022-10-18 17:53 ` tromey at sourceware dot org 2022-10-31 14:57 ` tromey at sourceware dot org 2022-10-31 14:59 ` 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-29243-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).