Daniel Stenberg wrote:
> On Mon, 20 Oct 2008, Yang Tse wrote:
>
>> Now the question is. Do I leave it in for debug-enabled builds or do I
>> simply wipe it out?
>
> I think you can wipe them completely since the debug-code already does
> something similar with the memdebug-system, and on linux at least of
> those errors are trapped with valgrind.

Also, some malloc implementations offer this natively. For instance on
OS X you can set MallocScribble and MallocPreScribble. Of course you may
not have access to OS X but if you do it's a good place to debug malloc
problems. For all I know these features may have been inherited from *BSD.

MB
Received on 2008-10-21