Date: Fri, 28 May 2004 17:09:59 +0200 From: "Willem Jan Withagen" <wjw@withagen.nl> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: freebsd-current@freebsd.org Subject: Re: Possible bug in malloc-code Message-ID: <08b401c444c5$d8545cb0$471b3dd4@dual> References: <7261.1085755951@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> > >If amd64-owners want to have a go at it, and see what they get: > > cd /usr/ports/devel/cocktail/ > > make > > cd work/cocktail-9309/reuse/m2c > > make test > > ./rMemoryDrv > > I get > hex# ./rMemoryDrv > Alloc: n = 0, ADR = 00000800 > Alloc: n = 0, ADR = 00000800 > Segmentation fault (core dumped) > hex# setenv MALLOC_OPTIONS V > hex# ./rMemoryDrv > Alloc: n = 0, ADR = 00000000 > Alloc: n = 0, ADR = 00000000 > Segmentation fault (core dumped) Ahh, right sorry, there was also a typo in the package which I did not put a PR out for to get it in the port, since I was trying to get it all to work on 64bits platforms in rMemory.c on line 148. s/__FREEBSD__/__FreeBSD__/ Which I did not catch on i386, since in a vague way the uppercase variant is also known when I compile. (No time taken to figure out where it comes from, or why amd64 does not have it) Apriciate it very much if you'd care to try again. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?08b401c444c5$d8545cb0$471b3dd4>