From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0AD2A382FCB0; Thu, 24 Nov 2022 17:21:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0AD2A382FCB0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669310478; bh=HOieV2vPEgqz1Z3okYQcEvDZZLt/U30OVJ+9Bcw/pUE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=NQVNhm19s7uLsSZZJifbaNLInouZYIY60ROpCRifLkWHhViKUaHLhDmn/FIhlz5wd hNJfAKYh5yPuMFjgZdGWcLmHWvJ8GHKKXbj4CVbTBG3oonJ34O54qM8SLFFlF34uWG xSmZpdx2g+xsgMo/9dLZq+MickhWUy26I38jf6qE= From: "arnout at mind dot be" 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:21:17 +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: arnout at mind dot be 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 #18 from Arnout Vandecappelle --- trace-symbol points to the same libgcc object that pulls in __register_fram= e: libgcc.a(unwind-dw2-fde-dip.o) The question however is why unwind-dw2-fde-dip.o gets pulled in. The map fi= le tells us that: /.../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_FDE) So my guess is that the problem really is in libgcc? --=20 You are receiving this mail because: You are on the CC list for the bug.=