From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id C083E3884579; Wed, 26 Oct 2022 18:54:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C083E3884579
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1666810488;
	bh=DuwYeOEo0d9aqGicbOCwu5lK2p40su5KelQPCwGmWVU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=N1KNnYU/4sLgqnC9ryIUvFMTu3Xxobaxh4iD2RveDgl3swtbosjwiB73coeNtLFK/
	 7NB0OVHLKppxueyCCYZomKKMBxYTTN1r1XeLmXKn7OIcjLeEg0f+QkK9xA2Vbaap59
	 +Mlw817WkHhY11wFeXOic64E1kH56f651pmYk/Xk=
From: "james.hilliard1 at gmail dot com" <sourceware-bugzilla@sourceware.org>
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: Wed, 26 Oct 2022 18:54:47 +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: james.hilliard1 at gmail 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: <bug-29621-131-rYd3NQHrpz@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29621-131@http.sourceware.org/bugzilla/>
References: <bug-29621-131@http.sourceware.org/bugzilla/>
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: <glibc-bugs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29621

--- Comment #4 from James Hilliard <james.hilliard1 at gmail dot com> ---
(In reply to Adhemerval Zanella from comment #3)
> Is there an easy way to reproduce it without resorting to build/use
> buildroot? I am trying to use the command you posted but it fails after
> downloading the kernel and I do not want to dig into builroot to debug th=
is.
>=20
> Also, could you verify what buildroot is doing differently than glibc own
> toolchain build script [1] so we can narrow down issue?
>=20
> [1]
> https://sourceware.org/git/?p=3Dglibc.git;a=3Dblob;f=3Dscripts/build-many=
-glibcs.
> py;h=3D5af6f369ae04027911b3407c64716dd1571eae6a;hb=3DHEAD

Hmm, what's the error message buildroot gives?

I'm not really sure how to reproduce outside of buildroot. Kind of hard to
narrow down what difference is triggering the issue with the toolchain build
script.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=