From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D32EE3858425; Fri, 23 Dec 2022 19:10:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D32EE3858425 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1671822656; bh=5B8ZBWa9VfOG5BvzRvxerfZ6yCcu4H+nYi/Ao0Tj/2I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yeTNnzkSxMNgCEus76nwzNe1Wr89rIHrMRm/JLdmrzltit/c8zsgbCjg023u4i6GB 3pmfrUW/f8w5qxKOYdMQmuFN0QvKbC5fkpiKq+pt2zY2VQ038ZavYA9KS4OuGN/e1U aOnH8ajPedZliSXbpFUKWqcCaA/jwPjKkcvaSwdI= From: "tromey at sourceware dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: NOTABUG X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D20837 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTABUG CC| |tromey at sourceware dot o= rg Status|UNCONFIRMED |RESOLVED --- Comment #1 from Tom Tromey --- 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=