Re: quick malloc guard patch

2005-06-06 Thread Ted Unangst
On Wed, 25 May 2005, Ted Unangst wrote: > it is part of G. we will wait to see what effects it has. and now it's option P. for some apps, it interfered with normal operation too much. -- And that's why he won't get my vote.

Re: quick malloc guard patch

2005-05-25 Thread Ted Unangst
it is part of G. we will wait to see what effects it has. -- quit whining you haven't done anything wrong because frankly you haven't done much of anything

Re: quick malloc guard patch

2005-05-25 Thread Hannah Schroeter
Hello! On Wed, May 25, 2005 at 03:17:59PM +0200, Janne Johansson wrote: >[...] >This would make all 4/8-byte mallocs take up one page(4k) each if I >understand this correctly. >That's fine for debugging, but probably too expensive for normal usage. I tend to agree. While most applications will

Re: quick malloc guard patch

2005-05-25 Thread Janne Johansson
Jonathan Thornburg wrote: >> when malloc gets a request with a size equal to the size of a pointer, we >> can allocate a whole page, and return a pointer 4 bytes from the end. >> the >> four bytes allocated are useable, but don't touch the fifth or any later >> ones. (8 bytes on 64bit archs). >