Re: Possible bug in malloc-code

From: Willem Jan Withagen <wjw_at_withagen.nl>
Date: Fri, 28 May 2004 17:09:59 +0200
----- Original Message ----- 
From: "Poul-Henning Kamp" <phk_at_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
Received on Fri May 28 2004 - 06:14:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:55 UTC