public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/20837] Destructor appears twice in the stack trace
Date: Fri, 23 Dec 2022 19:10:56 +0000 [thread overview]
Message-ID: <bug-20837-4717-rlfhWV84A4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20837-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20837
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
CC| |tromey at sourceware dot org
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Hi. This is not a gdb bug, but instead a detail of how C++
is implemented by your compiler. This is expected in the
ABI used by Linux. If you search for "in charge destructor"
you might find more information about why this is done.
I'm going to close this.
--
You are receiving this mail because:
You are on the CC list for the bug.
parent reply other threads:[~2022-12-23 19:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-20837-4717@http.sourceware.org/bugzilla/>]
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-20837-4717-rlfhWV84A4@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: link
Be 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).