http://bugs.winehq.org/show_bug.cgi?id=32554
--- Comment #12 from Ken Sharp kennybobs@o2.co.uk 2013-08-07 20:55:10 CDT --- Created attachment 45537 --> http://bugs.winehq.org/attachment.cgi?id=45537 Wine 1.7.0 console output with Valgrind
WINEDEBUG=warn+heap doesn't produce anything new in the console, but reduces the failure from 10% to 2%. Ran around 400 times in a loop.
Valgrind exits way too early to be useful but I've uploaded the log anyway.
Valgrind --trace-children=yes seems to break something as wineserver doesn't even start. I'm pretty sure it's Valgrind's fault:
==17766== Command: /home/ken/wine32/loader/wine-preloader /home/ken/wine32/loader/wine msiexec /i /home/ken/.cache/winetricks/dotnet30sp1/XPSEP\ XP\ and\ Server\ 2003\ 32\ bit.msi ==17766== preloader: Warning: failed to reserve range 00110000-68000000 ==17766== Warning: set address range perms: large range [0x82000000, 0xbec50000) (noaccess)
valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.
Valgrind on Ubuntu 12.06 AMD64 is utterly useless thanks to their broken multilib.
Unless someone knows how to get Valgrind to work with Wine (I'm pretty sure it used to work fine for me!) then I can't get anything sensible out of it.