http://bugs.winehq.org/show_bug.cgi?id=20852
Summary: Strange memory corruption in test_FindFirstChangeNotification Product: Wine Version: 1.1.33 Platform: PC OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
http://kegel.com/wine/valgrind/logs/2009-10-21-19.42/vg-kernel32_change.txt (and probably for as long as I've been running valgrind) have the warning
Invalid write of size 4 at RtlFreeAnsiString (rtlstr.c:170) by RemoveDirectoryW (path.c:1350) by RemoveDirectoryA (path.c:1364) by test_FindFirstChangeNotification (change.c:182) by func_change (change.c:883) by run_test (test.h:535) by main (test.h:585) Address 0x7f21eeac is on thread 1's stack
Inserting a function call in RemoveDirectoryW() (anywhere) sometimes makes the warning go away.
It seems that the first function call after the unix rmdir() at http://source.winehq.org/source/dlls/kernel32/path.c#L1349 triggers this warning... even if the function call is just a print statement.
To reproduce: install valgrind (after applying the workaround for the regression that keeps wine from working, https://bugs.kde.org/show_bug.cgi?id=205541#c1 ) build wine cd ~/wine-git/dlls/kernel32/tests ~/wine-git/wine winemine & valgrind --trace-children=yes ~/wine-git/wine kernel32_test.exe.so change.c
It still happens if I comment out all but test_FindFirstChangeNotification() at the bottom of change.c.
This could also be a bug in valgrind, I suppose; I filed an issue there for this a while ago as https://bugs.kde.org/show_bug.cgi?id=211701