http://bugs.winehq.org/show_bug.cgi?id=16621
--- Comment #3 from Garry albert.garry@ymail.com 2008-12-27 15:34:36 --- Created an attachment (id=18252) --> (http://bugs.winehq.org/attachment.cgi?id=18252) Extract from a WINEDUG command
My previous report was quite wrong : the console output is already displayed before I press the key. So I think it is useless.
I tried to come with a more useful bit of information. Attached is an extract of the log resulting from :
WINEDEBUG=+actctx,+atom,+comm,+computername,+console,+debugstr,+dll,+dosmem,+environ, +file,+fixup,+global,+int,+io,+loaddll,+local,+module,+nls,+powermgnt,+process,+profile, +reg,+resource,+seh,+selector,+snoop,+stress,+sync,+syslevel,+system,+tape,+task,+thread, +thunk,+time,+toolhelp,+ver,+volume,+vxd,+Heap
+relay produce a HUGE log file (like 500MB expanding over an over)
I understand almost nothing to the log, but it seems to me that a pattern comes again and again.
A useful information a can give is : even if the game is frozen, the log file is expanding endlessly...