From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 094FD382FCBD; Thu, 24 Nov 2022 17:27:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 094FD382FCBD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669310823; bh=S+Pq5IcnCOD1sgybCbG28IuHY17pkOxdQEECq0Wv2Xg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=X2qKqDZs05KTLsKiESo7cfqxhmQxrNyow8L08Cybn8Ey7kVgEoxZQUG8at07AfPG7 v1KepSEchWIKvtuprqBRN0R0CiqduV1OpZpXHqKcyZflMHWoFVsTtMJ+yFOQXqeLrA kQtXKRz+shE+CGB6/fL2cpeX9uJUwuGGPd7WL96E= From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/29621] librtld.os: in function `__register_frame': libgcc/unwind-dw2-fde.c:136: undefined reference to `malloc' Date: Thu, 24 Nov 2022 17:27:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D29621 --- Comment #19 from Florian Weimer --- (In reply to Arnout Vandecappelle from comment #18) > trace-symbol points to the same libgcc object that pulls in > __register_frame: libgcc.a(unwind-dw2-fde-dip.o) >=20 > The question however is why unwind-dw2-fde-dip.o gets pulled in. The map > file tells us that: >=20 > /.../libgcc.a(unwind-dw2.o) > /.../libgcc.a(_umoddi3.o) (_Unwind_Resume) > /.../libgcc.a(unwind-dw2-fde-dip.o) > /.../libgcc.a(unwind-dw2.o) (_Unwind_Find_F= DE) >=20 > So my guess is that the problem really is in libgcc? It suggests that libgcc was built with -fexceptions, but without optimizati= ons. We can't support that on the glibc side at present. The libgcc functions we= use must not have a dependency on the unwinder. --=20 You are receiving this mail because: You are on the CC list for the bug.=