http://bugs.winehq.org/show_bug.cgi?id=19125
--- Comment #1 from Jörg Höhle hoehle@users.sourceforge.net 2009-06-30 02:37:12 --- The same NUL-byte pattern appeared outside of Wine's trace log in the \windows\temp\res*.tmp file produced by running winetest-1.1.24.exe: notification.c:80: Test failed: 373: expected function 3 got 6 notification.c:79: Test failed: 379: expected status 0x00000002 got 0x00000800 notification.c:80: Test failed: (0 marked as todo, 26 failures), 0 skipped. ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@6356416: expected function 3 got 8 winhttp:notification done (27) winhttp:url start dlls/winhttp/tests/url.c -
sock.c:604: simple_client (c4): server ready sock.c:505: select_server (c2): accepting client connection sock.c:505: simple_client (c3) connected ^@^@^@^@^@^@^@^@^@^@^@^@select_server (c2): accepting client connection sock.c:616: simple_client (c4) connected
And many more in pipe.c. I.e. in those situations where concurrency (e.g. client+server are running) matters.
This ain't a trivial bug. World-wide IT depends on the quality of logfiles ;) If you can't trust your logfiles, what can you trust?