https://bugs.winehq.org/show_bug.cgi?id=30526
--- Comment #6 from Sjors Gielen winehq@sjor.sg --- Created attachment 49773 --> https://bugs.winehq.org/attachment.cgi?id=49773 Relay log of running dxdiag, with d3d traces.
WINEDEBUG=+d3d,+winediag,+relay wine dxdiag
I'm having problems finding the true reason for the illegal instruction in this log.
It appears the last call to a d3d function is around 20% of the log file, and after that lots of registry calls still happen that don't immediately look like "cleanup after failure" to me.
GDB reports: trace:d3d:check_fbo_compat RB attachment call ok utils.c / 1412 [New LWP 18909]
Program received signal SIGILL, Illegal instruction. [Switching to LWP 18909] 0x78f532ca in ?? () (gdb) bt #0 0x78f532ca in ?? () #1 0x7dcf6bf0 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?)