http://bugs.winehq.org/show_bug.cgi?id=9777
--- Comment #18 from Pol remember.pol@gmail.com 2008-06-15 01:16:45 --- (In reply to comment #17)
(In reply to comment #16)
Well. 1.0rc2 compiles and runs (seemingly) just fine with 'test_write_events();' commented out of the 'Main program' section in dlls/ws2_32/tests/sock.c..
This fixes this bug.
I now realize that test_write_events() is defined in the same file so my next course of action is to upgrade to latest git version and then comment out lines within the test_write_events() definition instead of the call to the function itself.
I'm really curious about how disabling a test that's never run during normal Wine operation fixes this issue. However, I'm positive this test isn't 100% valid, as it fails on Windows XP and newer.
Looking forward to your test results.
Define 'normal'? Because this test is obviously being run in this context, otherwise this bug entry would not exist!
Also, what do you mean 'fails on Windows XP and newer'?
This also doesn't seem to make sense in this context.
Why would one be running Silencer via wine on top of Windows XP via MinGW/Cygwin?
Seriously if you're testing this bug by running Windows XP natively. You should ...go `fsck` yourself.