Valgrind memory leaks in winmm + mciwave
Dan Kegel
dank at kegel.com
Fri May 7 07:22:44 CDT 2010
On Fri, May 7, 2010 at 5:07 AM, <Joerg-Cyril.Hoehle at t-systems.com> wrote:
> Why did I never see winmm/mci in Dan Kegel's Valgrind logs?
You've just run into http://bugs.winehq.org/show_bug.cgi?id=20919
See http://code.google.com/p/winezeug/source/browse/trunk/valgrind/valgrind-daily.sh#53
...
# Disable any tests known to hang reliably
# http://bugs.winehq.org/show_bug.cgi?id=20919
touch dlls/kernel32/tests/process.ok
touch dlls/ole32/tests/marshal.ok
touch dlls/shdocvw/tests/webbrowser.ok
touch dlls/urlmon/tests/url.ok
touch dlls/winmm/tests/mci.ok
touch dlls/winmm/tests/wave.ok
It would be good to get those cleaned up.
(Stack frames like
==4325== ??? (in /.../dlls/winealsa.drv/winealsa.drv.so)
probably mean that the dll has been unloaded before the stack frame was
printed.)
- Dan
More information about the wine-devel
mailing list