public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/20837] Destructor appears twice in the stack trace
[not found] <bug-20837-4717@http.sourceware.org/bugzilla/>
@ 2022-12-23 19:10 ` tromey at sourceware dot org
0 siblings, 0 replies; only message in thread
From: tromey at sourceware dot org @ 2022-12-23 19:10 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-12-23 19:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-20837-4717@http.sourceware.org/bugzilla/>
2022-12-23 19:10 ` [Bug c++/20837] Destructor appears twice in the stack trace tromey at sourceware dot org
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).