https://bugs.winehq.org/show_bug.cgi?id=49301 --- Comment #2 from Stefan Dösinger <stefan(a)codeweavers.com> --- Created attachment 67312 --> https://bugs.winehq.org/attachment.cgi?id=67312 Add CFI info to call_thread_exit_func This patch makes threads exit properly for me. I think it goes in the right direction, but I would be highly surprised if all the numbers in it are correct. It specifies the call frame setup done at the start of start_thread(), because after the mov %sp points to the 'old' stack as set up in start_thread, not whatever happened before call_thread_exit_func was called. I am worried that gdb still can't unwind the backtrace through call_thread_exit_func and start_thread. I would expect to see signal_start_thread, thread.c:start_thread and then the pthread creation functions below call_thread_exit_func. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.