http://bugs.winehq.org/show_bug.cgi?id=31595
--- Comment #20 from kisak42@gmail.com 2013-03-25 15:32:11 CDT --- Created attachment 44014 --> http://bugs.winehq.org/attachment.cgi?id=44014 GDB backtrace attempt
I had a try at capturing a backtrace of the regression. This test was made using wine commit e87cb774d131963d2642d075977571585ec5da8d. ./capture contains: #!/bin/bash env WINEPREFIX="/home/kisak/.PlayOnLinux//wineprefix/UT3" WINEDEBUG=+tid,+mmdevapi,+winmm,+driver,+midi,+dsound,+dsound3d,+dmusic,+mci,+oss,+alsa,+coreaudio ~/wine-git/wine /home/kisak/.PlayOnLinux/wineprefix/UT3/dosdevices/c:/Program\ Files/Steam/Steam.exe steam://run/13210 sleep 3 UT3pid=`pgrep UT3.exe` gdb --pid $UT3pid
I could have kept going, but they all read about the same, I stopped when I got a gui message "Wine program crash" "Internal errors - invalid parameters received" I'm not sure how else to proceed except for putting start and stop warn messages around all of the changes in the commit. I'm running the 3.7.10 kernel with nvidia-drivers 313.26 these days.