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
Hello!
Valgrind 1.0.0 has been released. It's a memory debugger to x86 Linux.
More details here http://developer.kde.org/~sewardj/
Testing CVS mc with Valgrind in the default mode exhibited 3 bugs:
1) Matching for shell rules in ext.c was reading memory before the
filename if it was shorter
