http://bugs.winehq.org/show_bug.cgi?id=14867
--- Comment #6 from Dan Kegel dank@kegel.com 2009-11-27 19:08:31 --- Sorry for not getting back to you, Mikolaj!
The affected app is Google Chrome, the problem was still happening with the most recent source of wine and chrome, your patch still applies, and it seems to fix the problem. Can you submit the patch?
fwiw, the exact commands I used, after following the tips in http://winezeug.googlecode.com/svn/trunk/valgrind/doc/win32.html to build wine and valgrind, were:
svn checkout http://winezeug.googlecode.com/svn/trunk/ winezeug cd winezeug cat valgrind/valgrind-suppressions testsuites/chromium/chromium-valgrind-suppressions > ../supp.txt cd .. wget http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/33231/chrome-wi... unzip chrome-win32.zip wget http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/33231/chrome-wi... unzip chrome-win32-syms.zip cd chrome-win32 mv ../chrome-win32-syms/chrome_dll.pdb chrome.pdb /usr/local/valgrind-for-wine/bin/valgrind --trace-children=yes --track-origins=yes --workaround-gcc296-bugs=yes --suppressions=../supp.txt --leak-check=full --show-possible=no ~/wine-git/wine chrome --no-sandbox http://zilf.org > log.txt 2>&1
I then waited for zilf.org to show up, hit refresh a few times, and quit, then looked at log.txt.