https://bugs.winehq.org/show_bug.cgi?id=37310
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- Could you please also attach a log of the terminal output? (see: http://wiki.winehq.org/FAQ#get_log )
Besides that, a trace created in the following way could be useful: WINEDEBUG=+tid,+seh,+loaddll,+process wine your_program.exe >> /tmp/output.txt 2>&1 (see: http://wiki.winehq.org/FAQ#head-16da35b6327024d6ea576e3678488b16862d0f5e )
Does the program run on recent versions of Windows? The crash output is very weird, because its a privileged instruction exception, not an invalid memory access - this means the program expects to be able to do direct hardware access, which is even forbidden on Windows. (Except the error already happens earlier, and this is just the way the program uses to terminate?!)
Did the issue occur after an update of the software and/or wine ? Because the last AppDB report doesn't list this issue.
Regards, Sebastian