Joerg wrote:
I'm surprised that valgrind did not complain about the bug...
Looks like I ignore files that only contain leak errors: http://code.google.com/p/winezeug/source/browse/trunk/valgrind/valgrind-spli... on the theory that we're already overwhelmed dealing with non-leak errors.
You can still see the leaks in the full log, http://kegel.com/wine/valgrind/logs/2009-11-19-08.35.log
What do people think - should we focus on non-leak errors for a while (in which case I should suppress all leak errors), or should I stop ignoring modules that only have leak errors?
Also, mci tests hang on my system and need to be killed, so I may be missing some errors because of that.
(Finally, my automated runs are on hold while I add use-after-free detection. I'm lame, and use the same source tree for develoment and for the automated runs. One of these days I should separate them. Or somebody else could do the automated runs...) - Dan
Dan Kegel wrote:
Looks like I ignore files that only contain leak errors: You can still see the leaks in the full log, http://kegel.com/wine/valgrind/logs/2009-11-19-08.35.log
Ah, I was surprised to find no mention of winmm in the normal log ;)
should I stop ignoring modules that only have leak errors?
I was lulled into false confidence by not seing errors. Perhaps I'd have caught a message at the top of the web logs page.
Also, mci tests hang on my system and need to be killed, so I may be missing some errors because of that.
Hmm, you already mentioned this one earlier:
err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Resource temporarily unavailable
Is there anything you can change to your sound configuration to avoid it? I don't see why the winmm wave and capture tests pass while only mci generates hundreds of this warning. Can you run WINETEST_INTERACTIVE=1 wave.ok or capture.ok?
I've only seen this error sequence once or twice in my tests.
preloader: Warning: failed to reserve range 00110000-68000000
??
Regards, Jörg Höhle.
-
Dan Kegel -
Joerg-Cyril.Hoehle＠t-systems.com