Re: extent-patch and overview of what is supposed to follow

[Brett Lymn <blymn%baea.com.au@localhost>]

On Tue, Apr 05, 2011 at 10:37:37AM +0100, Mindaugas Rasiukevicius wrote:
> 
> I am not convinced about statistics point.  For intensive allocations,
> constant-sized pool_cache(9) should/would be used, where it already
> gathers statistics.  If there is some particular need for statistics,
> one can always collect it at the caller's level.  Therefore, I do not
> see the need to invade allocator's API for that.
> 

We shouldn't just consider statistics anyway, there were some useful
malloc debug facilities which allowed you to know what memory had been
allocated to what process.  I had extended that so you could tell what
processes had allocated next to the region of interest - I used this to
nail a rather nasty buffer overflow that was stomping on the memory
allocations of innocent parties.  I don't know how I could have tracked
that bug down without the level of information available from the malloc
debug logs.

-- 
Brett Lymn
"Warning:
The information contained in this email and any attached files is
confidential to BAE Systems Australia. If you are not the intended
recipient, any use, disclosure or copying of this email or any
attachments is expressly prohibited.  If you have received this email
in error, please notify us immediately. VIRUS: Every care has been
taken to ensure this email and its attachments are virus free,
however, any loss or damage incurred in using this email is not the
sender's responsibility.  It is your responsibility to ensure virus
checks are completed before installing any data sent in this email to
your computer."