Thanks I tried using mudflap which looked cool but does not work with shared libraries. valgrind is way to slow. This looks juuust right. I'm assumming MALLOC_CHECK_ is basically the same as electric fence i.e it puts in unmapped pages ?
Mike On 11/16/05, Clemens Kirchgatterer <[EMAIL PROTECTED]> wrote: > Mike Emmel <[EMAIL PROTECTED]> wrote: > > > On further testing of the patch and sent it to the list I got memory > > corruption problems similar to what you described how did you get glib > > to detect the double free ? > > man malloc: > > Recent versions of Linux libc (later than 5.4.23) and GNU libc (2.x) > include a malloc implementation which is tunable via environment vari- > ables. When MALLOC_CHECK_ is set, a special (less efficient) implemen- > tation is used which is designed to be tolerant against simple errors, > such as double calls of free() with the same argument, or overruns of a > single byte (off-by-one bugs). Not all such errors can be protected > against, however, and memory leaks can result. If MALLOC_CHECK_ is set > to 0, any detected heap corruption is silently ignored; if set to 1, a > diagnostic is printed on stderr; if set to 2, abort() is called immedi- > ately. This can be useful because otherwise a crash may happen much > later, and the true cause for the problem is then very hard to track > down. > > worked for me sometimes. > > best regards ... > clemens > > _______________________________________________ > directfb-dev mailing list > [email protected] > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
