Date: Fri, 28 May 2004 16:52:31 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Willem Jan Withagen" <wjw@withagen.nl> Cc: freebsd-current@freebsd.org Subject: Re: Possible bug in malloc-code Message-ID: <7261.1085755951@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 28 May 2004 16:24:39 %2B0200." <079001c444bf$830965d0$471b3dd4@dual>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <079001c444bf$830965d0$471b3dd4@dual>, "Willem Jan Withagen" writes: >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) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7261.1085755951>