[lug] Best way to locate a memory leak

[Scott Herod]

Yes.  Again I'll say how happy that I am with it.  I've even now sent off
a bug report to GNU about glibc recently.  (Ok, 2.2.5 so they probably
knew about it already but it was fun to do.)

Scott

On Thu, 6 Mar 2003, Daniel Webb wrote:

> 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
> >