public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/29243] infinite loop in generic_value_print Date: Mon, 31 Oct 2022 14:59:48 +0000 [thread overview] Message-ID: <bug-29243-4717-3NVHoy1LGX@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29243-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29243 --- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=86430497337968e6163aef370c6312e7b5ed6504 commit 86430497337968e6163aef370c6312e7b5ed6504 Author: Tom Tromey <tromey@adacore.com> Date: Tue Oct 18 11:32:52 2022 -0600 Fix regression in pointer-to-member printing PR c++/29243 points out that "info func" on a certain C++ executable will cause an infinite loop in gdb. I tracked this down to a bug introduced by commit 6b5a7bc76 ("Handle member pointers directly in generic_value_print"). Before this commit, the C++ code to print a member pointer would wind up calling value_print_scalar_formatted; but afterward it simply calls generic_value_print and gets into a loop. This patch restores the previous behavior and adds a regression test. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-31 14:59 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-10 23:46 [Bug c++/29243] New: " roland at gnu dot org 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 [this message]
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-3NVHoy1LGX@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).