On Nov 24, 7:54 am, sebast...@aperghis.net (Sébastien Aperghis- Tramoni) wrote: > [...] the thing that > really annoyed me recently was the lack of advanced debug tools, for example > to find memory leaks. None of the tools I found or was pointed to worked > in my case.
Allow me to recommend my own Test::Weaken. This is powerful enough that it has found a bug in Perl itself. It has received a lot of use for debugging Gtk2, so much so there's a spinoff: Test::Weaken::Gtk2. Test::Weaken works by creating weak references, then freeing the original memory objects. If all is working, and the original memory objects went away like they should, the weak references will now be undefined. If there are leaks, the weak links will point to the leaked memory. Jeffrey Kegler
