i love valgrind and have used it on gangliad many times (the reason i
have the short pth_sleep() is so that i can run gangliad for a fixed
time and generate a leak table).. right now i'm trying mpatrol (another
good memory tool).
ok.. i gave up on mpatrol, tried dmalloc and went back to valgrin
> i'm going to squash this bug asap.
Have you looked at Valgrind (http://valgrind.kde.org/). Linux/x86 only,
but if the leak is present in all implementations, you should be able to
catch it.
Regards,
Robert.
guys-
i'll be putting out a new snapshot soon. i'm tracking down a memory
leak right now (i need to build some more unit tests).
when i left work yesterday at 4:30pm i started a test that just hammered
a running gangliad with HTTP requests.
after running for 19 hours and answering 6,941,964 req
