http://bugs.winehq.org/show_bug.cgi?id=33974
--- Comment #8 from Mike Blumenkrantz michael.blumenkrantz@gmail.com 2013-07-08 00:00:33 CDT --- (In reply to comment #6)
I bet steam's crashhandler.dll or friends is catching them.
+seh can add a little info to the log about the crash, but probably isn't useful in and of itself.
(I wonder what happens if you disable crashhandler.dll.)
I'll test this and report back after work today.
(In reply to comment #7)
(In reply to comment #5)
(In reply to comment #4) I do get a 1.3gb core dump each time, however, and it is definitely crashing with SIGSEGV.
Hi,
If you use winedbg to open the core dump, could you get a backtrace?
$ winedbg xxx.dmp or somthing like that
Unfortunately the cores are truncated (despite having set them to unlimited size with ulimit). Loading them reveals a three frame stack with no symbols.