From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E80653858C74; Tue,  2 May 2023 14:16:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E80653858C74
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683037004;
	bh=u/W3wkP3TTkPZ0ncxLzO3Z6nFX3q79Yqxbpd+UENDOI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=PIaNlmML3KOuGwjzxhf++shkbjrn7JaV/112b3AsW92iAMHGgve79l9hkoi2Z72uP
	 JgtytXIWnXYhU57l7J/UATCzprNzwnL7WvZUWDEvdKyDiNCjrKe+PnF6TpkVNn4AlC
	 zfHMqyt7y2ofncfR1+RM9/OVezrXbNVdoKRMG9p8=
From: "tneumann at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/109685] [13/14 Regression] Memory leak in
 `__deregister_frame`
Date: Tue, 02 May 2023 14:16:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 13.1.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tneumann at users dot sourceforge.net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.2
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109685-4-9CamiH3XyH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109685

--- Comment #2 from Thomas Neumann <tneumann at users dot sourceforge.net> =
---
I can reproduce the issue. The attached patch fixes the problem, I will sen=
d it
for reviewing.=