http://bugs.winehq.org/show_bug.cgi?id=20380 --- Comment #80 from Gustaw Smolarczyk <wielkiegie(a)gmail.com> 2010-02-19 11:05:55 --- I'm not familiar with signals and pthread, but I'll try to help somewhat :) I can easily reproduce this "BUG" on my machine. It looks like kernel delays a SIGSEGV handler. SIGUSR1 handler is called first but it's immediatly interrupted by SIGSEGV. I can't see any way how "push ebp" could generate SIGSEGV (no stack manipulation here), so it's for me the only explaination. By blocking SIGSEGV in SIGUSR1 sigaction the BUG disappears, but it's not the best way, I think. Is the SIGSEGV blocked in the whole handler? Or just pending SIGSEGVs are blocked for a while? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.