[lug] Best way to locate a memory leak

[Scott Herod]

Check valgrind from the KDE group.

http://developer.kde.org/~sewardj/

I've run it against apache in the past.  (Not sure if that's what you're
using.)

Scott

On Tue, 4 Feb 2003, Elyse Grasso wrote:

> Our web and mail server may be running something that has a memory leak.
> Most likely on the webserver side. What tools do people like for
> tracking things like this down?
>
> We've recently added some large downloadable files on our website, as
> well as the BURP tool for registering visitors to the download site.
> Could either of these be the culprit? What's the best way to find out?
> --
> Elyse Grasso