https://bugs.winehq.org/show_bug.cgi?id=47320
--- Comment #13 from minion minion.procyk@gmail.com --- thanks for working on this team, application doesn't seem to fail on gdi32 anymore. It gets a little farther. Upon pressing play I get a window popup that disappears soon after showing. Seems like the game is trying to do some property handling and fails to get/set something and abruptly exits.
-- snip -- 03d4:03dc:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,9,0x1b8bf78,8,(nil)) 03d4:03dc:trace:seh:NtSetInformationThread (0xfffffffffffffffe,17,0x1b8ede8,1) 03d4:03dc:trace:seh:NtSetInformationThread (0x48e897101e554,17,(nil),0) 03d4:03dc:trace:seh:NtSetInformationThread (0xfffffffffffffffe,17,(nil),0) 03d4:03dc:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,17,0x1b8ede8,4,(nil)) 03d4:03dc:trace:seh:NtQueryInformationThread (0x48e89710e4842,17,0x1b8ede8,4,(nil)) 03d4:03dc:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,17,0x1b8ede8,1,(nil)) 03d4:03e0:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,9,0x1c9bf78,8,(nil)) 03d4:03e0:trace:seh:NtSetInformationThread (0xfffffffffffffffe,17,0x1c9ede8,1) 03d4:03e0:trace:seh:NtSetInformationThread (0x48e89712ca7fe,17,(nil),0) 03d4:03e0:trace:seh:NtSetInformationThread (0xfffffffffffffffe,17,(nil),0) 03d4:03e0:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,17,0x1c9ede8,4,(nil)) 03d4:03e0:trace:seh:NtQueryInformationThread (0x48e8971374554,17,0x1c9ede8,4,(nil)) 03d4:03e0:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,17,0x1c9ede8,1,(nil)) 03d4:03dc:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFFFFFFFFFA, 0000000001B8FE10 03d4:03e0:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFFFFFFFFFA, 0000000001C9FE10 03d4:03e0:trace:seh:NtSetInformationThread (0xfffffffffffffffe,3,0x1c9fdcc,4) 0078:0088:trace:seh:NtQueryInformationThread (0x364,0,0xeaf730,30,(nil)) 03d4:03d8:trace:seh:dispatch_exception code=80000003 flags=0 addr=000000014236DD08 ip=4236dd07 tid=03d8 03d4:03d8:trace:seh:dispatch_exception info[0]=000000000021fad0 03d4:03d8:trace:seh:dispatch_exception rax=000000000021fad0 rbx=0000000044c4a720 rcx=000000007bc692a0 rdx=00000000000a85a8 03d4:03d8:trace:seh:dispatch_exception rsi=0000000000000000 rdi=0000000000000000 rbp=000000000021fab0 rsp=000000000021fa78 03d4:03d8:trace:seh:dispatch_exception r8=0000000000000038 r9=0000000040000470 r10=0000000000000038 r11=0000000000010138 03d4:03d8:trace:seh:dispatch_exception r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 03d4:03d8:trace:seh:call_vectored_handlers calling handler at 0000000152D14241 code=80000003 flags=0 03d4:03d8:trace:seh:call_vectored_handlers handler at 0000000152D14241 returned ffffffff -- snip --
not sure if this is relevant but process is also having trouble reading some thread info which gets a spammed a few times.
-- snip -- 03d4:03e8:warn:seh:get_thread_times Failed to open /proc/34351/stat: No such file or directory 0140:0144:warn:seh:get_thread_times Failed to open /proc/34351/stat: No such file or directory -- snip --
and then it tries to set the language for the game
-- snip -- 03d4:03d8:fixme:nls:get_dummy_preferred_ui_language (0x8 000000000021E740 0000000000000000 000000000021E744) returning a dummy value (current locale) 03d4:03d8:fixme:nls:get_dummy_preferred_ui_language (0x8 000000000021E740 00000000000A9680 000000000021E744) returning a dummy value (current locale) 03d4:03d8:fixme:nls:RtlGetThreadPreferredUILanguages 00000008, 000000000021C6E0, 0000000000000000 000000000021C6E4 03d4:03d8:fixme:nls:get_dummy_preferred_ui_language (0x8 000000000021C6E0 0000000000000000 000000000021C6E4) returning a dummy value (current locale) 03d4:03d8:fixme:nls:RtlGetThreadPreferredUILanguages 00000008, 000000000021C6E0, 00000000000A9686 000000000021C6E4 03d4:03d8:fixme:nls:get_dummy_preferred_ui_language (0x8 000000000021C6E0 00000000000A9686 000000000021C6E4) returning a dummy value (current locale) 03d4:03d8:fixme:nls:RtlSetThreadPreferredUILanguages 8, 00000000000A9680, 000000000021C6E0 -- snip --
and then it fails. i find this strange because the application fails right after the error below but i would find it strange that a usb event error would cause the application to crash.
-- snip -- 0078:00a4:err:wineusb:event_thread_proc Error handling events: System call interrupted (perhaps due to signal) -- snip --
these are the relevant bits but il also upload an seh log