Hi!

Sometime ago someone suggested using "Valgrind" to test our memory management.

That was me :-)

After reading its docs, it looks quite worth a try!

Cool.

As using Valgrind to test dillo is akin to using efence (mostly userland), I thought it may be very well done while I keep working on dillo internals.

Is anyone interested?

I would, but unfortunately it really requires a faster machine than I've got available - running code under Valgrind is a *lot* slower than running it natively.

The home page is at: http://developer.kde.org/~sewardj/

Note that most probably the development version is required because dillo uses several threads (POSIX).

John.