Re: Valgrind vs. MAD

[Miguel de Icaza <miguel ximian com>]

Hello,

> Although Valgrind is currently limited to one OS and one architecture, it 
> does such a great job, that we should consider removing MAD (memory 
> allocation debugger) from the MC sources.

This is a very good idea.  In the past very few developers used MAD if
any, mostly those debugging the system.  Given the wild distribution of
Linux, it might make sense to just drop support for MAD.  Less code to
maintain is always good.


> As for distinguishing between g_malloc() and malloc(), it can be done with
> Valgrind by redirecting malloc() and free() to some alternative memory
> manager while keeping g_* functions intact.  I don't think it's worth the
> trouble to distinguish between g_malloc() and malloc(), as long as we stay
> with glib-1.2.

yep.

Miguel