[Bug 19125] log file corruption on dual-core MacOS

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=19125





--- Comment #5 from Jörg Höhle <hoehle at users.sourceforge.net>  2010-01-29 03:31:35 ---
On 2010-01-28, Stefan Leichter reported a similar problem with
AMD Phenom(tm) II X2 550 Processor on a NVIDIA GeForce 8300 
Chipset running running Debian Lenny 32 bit
http://www.winehq.org/pipermail/wine-devel/2010-January/081406.html

The work-around on Debian is the same as on MacOS: Use ">>" to open the log in
append mode.

So log write contention is not a MacOS-specific issue.  However, Stefan does
not notice NUL-bytes in the log. Instead, log line endings are cut off, so 2
logs appear on the same line like this:
003b:Call KERNEL32.lstrlenW(01812a90 L"C:\\windows\\temp\\PCULog0.0038:Call
user32.Un003b:Ret  KERNEL32.lstrlenW() retval=0000001b ret=01523b41

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.