http://bugs.winehq.org/show_bug.cgi?id=17232
--- Comment #11 from Anastasius Focht focht@gmx.net 2009-04-25 02:00:14 --- Hello,
--- quote --- When I run the command from #9, on first run crash.txt is empty. Only on the second run I get output there.
Do you want me to post that or is it useless, as far as this bug is concerned? --- quote ---
Well, if that command line doesn't work for you due to different crash/exception message or process doesn't exit (pipe), ctrl+c, you might try to split it up, e.g. first let it create the relay log:
--- snip --- WINEDEBUG=+tid,+seh,+relay wine start.exe >relay.log 2>&1 --- snip ---
and then filter out only the relevant parts:
--- snip --- grep -A 50 -B 4000 "AccessViolationException" relay.log >crash.txt --- snip ---
If the second step still leaves an empty file, there might be a different bug. Just keep trying (install+start) until you see parts of the CLR backtrace:
--- snip --- ... Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at System.Drawing.SafeNativeMethods.Gdip.GdipCreateFontFromLogfontW(HandleRef hdc, Object lf, IntPtr& font) at System.Drawing.Font.FromLogFont(Object lf, IntPtr hdc) at System.Drawing.Font.FromHfont(IntPtr hfont) at System.Drawing.SystemFonts.get_DefaultFont() at System.Windows.Forms.Control.get_Font() ... --- snip ---
If that relay.log isn't too large you attach it as plain text file. Otherwise compress it (bzip2) and attach it to this bug like you did with the other logs. Just make sure it contains the backtrace as shown above.
Regards