Date: Mon, 31 May 2004 22:51:34 +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: <2675.1086036694@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 31 May 2004 22:41:57 %2B0200." <0be501c4474f$bb115400$471b3dd4@dual>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <0be501c4474f$bb115400$471b3dd4@dual>, "Willem Jan Withagen" writes: > > i = 11 >Alloc: n = 335544320, ADR = 0x00000000485D7000 >Alloc: n = 402653184, ADR = 0x000000005C5D7000 >Alloc: n = 469762048, ADR = 0x00000000745D7000 >Alloc: n = 536870912, ADR = 0xFFFFFFFF905D7000 >Free: n = 536870912, ADR = 0xFFFFFFFF905D7000 >rMemoryDrv in free(): error: junk pointer, too high to make sense >Abort (core dumped) As for this part: Does the program in fact have a prototype for malloc(3) in sight ? Can you try to explicitly add a wrong prototype to see that it complains ? Alternatively, #include <stdlib.h> to get it a prototype. I looked briefly at the source code of the test-program and while I am in a position to say that it is doing something wrong with the casting, it does look mightily bogus to me. Poul-Henning -- 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?2675.1086036694>