Date: Wed, 11 Sep 2002 12:18:34 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: John Polstra <jdp@polstra.com> Cc: stable@FreeBSD.ORG Subject: Re: Malloc backwards compat problem in stable as of yesterday ? Message-ID: <20020911021834.GA92749@gsmx07.alcatel.com.au> In-Reply-To: <200208210155.g7L1tiJx083675@vashon.polstra.com> References: <20020820222727.GC407@axiom.niw.com.au> <200208210155.g7L1tiJx083675@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-Aug-20 18:55:44 -0700, John Polstra <jdp@polstra.com> wrote: >Yes, and what a pain! For any program linked against a recent >libc but run against a slightly older one, malloc fails on >all calls. I looked into it a bit, and found that sbrk() is >returning garbage. I'm fairly certain the cause was this commit to >"src/lib/libc/i386/sys/sbrk.S": > > revision 1.7.2.1 > date: 2002/08/12 14:23:29; author: kan; state: Exp; lines: +3 -3 > MFC 1.11: Use '_end' symbol instead of 'end' to initialize minbrk > and curbrk variables. > > Approved by: obrien Having also been bitten by this one... I initially worked around it by upgrading my systems to be recent enough to avoid the problem. But I've now worked myself into a bit of a corner: My development systems all have sbrk.S v1.7.2.1 but I have a need to install a binary onto some older -stable machines - which I can't afford to upgrade at present. Any suggestions on a work-around other than static linking? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020911021834.GA92749>