[lug] Best way to locate a memory leak

[Daniel Webb]

A little late the conversation, but I'll throw in my 2 cents: Valgrind is
the best programming tool on my computer.  It has saved my butt many
times.  I haven't even used the memory leak features, but the bad memory
accesses it finds are amazing.  There were (are) many production level
packages that have memory problems detected by Valgrind.

On Wed, 5 Feb 2003, Scott Herod wrote:

> 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
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>