Date: Mon, 24 Jul 1995 14:48:04 +0300 From: Gennady Sorokopud <gena@NetVision.net.il> To: Poul-Henning Kamp <phk@freefall.cdrom.com> Cc: <hackers@freebsd.org> Subject: RE: new malloc.c please test Message-ID: <XFMail.950724122948.gena@NetVision.net.il> In-Reply-To: <199507241032.DAA14618@freefall.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! I just tried it and after installing new libc my system started to misbehave. Many programs (like vi) complained about memory allocation and my Xserver just crashed. I'm running -current (supped yesterday) and i compiled malloc exactly like you said. ( i defined j in free_pages and also i got 2 warnings during compilation: FreeBSD i386 constants hardcoded. i386 inline assembly used. but i guess it's ok) In message <199507241032.DAA14618@freefall.cdrom.com> Poul-Henning Kamp writes: >OK, here is the next version of my "new" malloc.c This one is running >in my libc right now, and giving no problems so far. > >Please give it a whirl: > cp malloc.c /usr/src/lib/libc/stdlib > cd /usr/src/lib/libc > make all install > >In particular I am very interested in data regarding performance, time and >resource wise compared to the regular malloc in libc, -lgnumalloc and so >on. If some of you could roll it into a Xserver I would be very interested >in the results, and likewise what impact it has on "make world" kind of >things. > >If you compile with -DSANITY it will core-dump the program if it detects >bad pointers or metadata. > >If you have time, you can try to fiddle with the "NFP" definition, and >see what it buys you. > >Please email all results to me. > >Poul-Henning >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.950724122948.gena>