http://bugs.winehq.org/show_bug.cgi?id=18924
--- Comment #8 from Anastasius Focht focht@gmx.net 2009-06-14 13:19:50 --- Hello,
--- quote --- It's not clear at all from the original bug report what the reporter complains about, and what exactly is the functionality is needed, and is that really about OutputDebugString sending info to the debugger. --- quote ---
I think it was pretty clear as he described the current OutputDebugString() behaviour and apps which act as "debug message monitor" relying on proper implementation to actually "see" the debug messages. A simple string dump on main executable (after unpacking with UPX) reveals:
--- snip --- $ strings FF7Music.exe | grep DBWIN DBWIN_BUFFER_READY DBWIN_DATA_READY DBWIN_BUFFER --- snip ---
So yes, the app relies on proper OutputDebugString() implementation which Wine currently lacks.
The current implementation can be enhanced by keep sending the message buffer to Wineserver - preserving existing interaction with usermode debuggers - _and_ write the message buffer into shared section if present.
Some tools that can be used for testing (in addition to the link from my previous comment):
"DebugView" from infamous sysinternals team (now M$): http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
"Hoo WinTail": http://www.hootech.com/WinTail/
"DbMon.NET - A simple .NET OutputDebugString capturer": http://www.codeproject.com/KB/trace/DbMonNET.aspx
Regards