Re: [Valgrind-users] Omega - Release Candidate 1 Announcement

[Bob R. <bob...@co...>]

On Sat, Sep 23, 2006 at 05:50:07PM +0100, Bryan Meredith wrote:
> Fellow Valgrinders,
> 
> please see http://www.brainmurders.eclipse.co.uk/omega.html for a
> complete overview of what this tool can do for you!
> 
> (We use this heavily at work - feel free to give it a spin...)
> 
> As ever, I would welcome your comments, bug reports and especially any
> news of success stories. Please share them with us on the list and copy
> me in so I don't miss them.

Hi, 

I just installed valgrind with omega support. valgrind was reporting a
memory leak with the memcheck tool, and I spent a good 2 hours trying to
figure out if it was a leak or not, cause I couldn't find WHERE it
leaked.

After running with the omega tool, I'm now confronted with 122
memory leaks, where as the memcheck was saying I only had 2.

It looks like omega is not honoring the suppressions when reporting
on memory leaks, is this true?

Also, I was only trying to fix the "definatly" lost instances of 
memory leaks that memcheck found. Then I was going to turn on leak
checking in the nightly test suite. At that point, I could then continue
to fix the rest of the memory leaks memcheck found (ie. indirect lost).

So, two more questions.

Why does omega find so many more memory leaks than memcheck?
Are they real leaks or false positives?

Can omega total the memory leaks that it found and report a number the
way memcheck does? That number usually provides a "wow factor" to people
explaining to there boss that they just stopped the coffee brewing 
network application from leaking 100 megs of memory each time a pot of
coffee is brewed ...

Thanks,
Bob Rossi