Date: Fri, 13 Jan 2006 21:53:19 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: freebsd-current@freebsd.org, Jason Evans <jasone@freebsd.org> Subject: Re: HEADSUP: malloc changeover Message-ID: <20060113195319.GA17963@flame.pc> In-Reply-To: <14547.1137178334@critter.freebsd.dk> References: <1A89617A-5F0E-492E-8C21-10A4F679BCD2@freebsd.org> <14547.1137178334@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-01-13 19:52, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote: >In message <1A89617A-5F0E-492E-8C21-10A4F679BCD2@freebsd.org>, Jason Evans writes: >> The most likely types of application bugs that this malloc >> implementation will uncover are: > > And speaking from experience: You can do Jason a big favour by > trying your app with Electric Fence or similar before yelling > at him. HEH! Definitely. I have built & run at least four versions since January 11, two with DEBUG_FLAGS='-g' for both userland and kernel and two without. As Jason said, we should probably keep looking for potential problems both in the new malloc() and the programs that use it, but the fact that my laptop still runs quite fine with several dozens of ports installed some time back in December seems to imply there aren't any _really_ _nasty_ bugs in malloc so far Jason, thanks for the work you've put into this :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060113195319.GA17963>