Date: Thu, 27 Nov 2003 22:54:08 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Kris Kennaway <kris@obsecurity.org> Cc: ia64@FreeBSD.org Subject: Re: GNU configure and rpl_malloc (Re: adtool-1.2 broken on ia64) Message-ID: <20031128065408.GA16995@dhcp01.pn.xcllnt.net> In-Reply-To: <20031128060214.GA79146@xor.obsecurity.org> References: <20031127132731.GK67207@xor.obsecurity.org> <20031127183129.V30085@randomservers> <20031128032723.GA77578@xor.obsecurity.org> <20031128045554.GB16503@dhcp01.pn.xcllnt.net> <20031128060214.GA79146@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 27, 2003 at 10:02:14PM -0800, Kris Kennaway wrote: > On Thu, Nov 27, 2003 at 08:55:54PM -0800, Marcel Moolenaar wrote: > > > It's a broken configure script. The problem is that malloc(0) > > returns NULL on ia64, which is incompatible with GNU malloc > > (apparently). This automaticly and bogusly results in the > > redefinition of malloc as rpl_malloc. On i386, malloc(0) returns > > 0x800. > > Ick..that's a lot of bogusness. Is this a design choice? It may be > worthwhile to revert it for now so that all those ports don't fail. I think it's an unfortunate side-effect of adapting to the pagesize. We never get to call malloc_init(), because malloc(0) takes a shortcut out (i.e it doesn't call imalloc()). Anyway: I removed the particular ia64 behaviour on the ia64 branch in perforce. I probably want to get this into 5.2. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031128065408.GA16995>