public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109064] Maximum recursion depth exceeded in std::shared_ptr xmethod Date: Thu, 27 Apr 2023 23:04:30 +0000 [thread overview] Message-ID: <bug-109064-4-lR2Hz8HJEF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109064-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109064 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:cc75195ee8811d6c48f05727c170916c0adc227b commit r10-11320-gcc75195ee8811d6c48f05727c170916c0adc227b Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Mar 10 11:06:25 2023 +0000 libstdc++: Fix GDB Xmethod for std::shared_ptr::use_count() [PR109064] libstdc++-v3/ChangeLog: PR libstdc++/109064 * python/libstdcxx/v6/xmethods.py (SharedPtrUseCountWorker): Remove self-recursion in __init__. Add missing _supports. * testsuite/libstdc++-xmethods/shared_ptr.cc: Check use_count() and unique().
next prev parent reply other threads:[~2023-04-27 23:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-08 12:04 [Bug libstdc++/109064] New: " ks1322 at gmail dot com 2023-03-08 16:17 ` [Bug libstdc++/109064] " ks1322 at gmail dot com 2023-03-10 10:37 ` redi at gcc dot gnu.org 2023-03-10 11:36 ` redi at gcc dot gnu.org 2023-03-10 11:36 ` cvs-commit at gcc dot gnu.org 2023-03-10 11:37 ` redi at gcc dot gnu.org 2023-03-20 11:54 ` cvs-commit at gcc dot gnu.org 2023-04-27 22:01 ` cvs-commit at gcc dot gnu.org 2023-04-27 23:04 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-27 23:05 ` redi 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-109064-4-lR2Hz8HJEF@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).