https://bugs.winehq.org/show_bug.cgi?id=56359
--- Comment #4 from Eric Pouech eric.pouech@gmail.com --- thanks for the log
what seems to happen is - Ctrl-C is caught on console and sent to debuggee (good) ``` Ctrl-C: stopping debuggee ``` - signal handler in debuggee creates the console event dispatch thread, and debuggee catches the thread creation events (good) ``` 0118:trace:winedbg:dbg_handle_debug_event 011c:0130: create thread D @00007F08D1B229B0 ``` - but this crashes immediately, moreover at the very address of the start of the thread ``` 0118:trace:winedbg:dbg_handle_debug_event 011c:0130: exception code=c0000005 0118:trace:winedbg:dbg_handle_exception exception=c0000005 first_chance=Y 0118:trace:winedbg:dbg_handle_debug_event 011c:0130: exception code=c0000005 Unhandled exception: page fault on execute access to 0x00007f08d1b229b0 in 64-bit code (0x007f08d1b229b0). ```
(and afterwards - actually winedbg restarts because the access violation isn't handled by first instance - the faulty address isn't present in process address space)
as I can't repro here, I'll ask for more info (esp. to try to grasp where we end up in this faulty address)
could send back the log (+winedbg) of the session, using the following winedbg commands
info share info maps p &ntdll.so!p__wine_ctrl_routine disas ntdll.so!p__wine_ctrl_routine watch * &ntdll.so!p__wine_ctrl_routine cont
TIA