http://bugs.winehq.org/show_bug.cgi?id=19055
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #1 from Anastasius Focht focht@gmx.net 2009-06-23 16:49:39 --- Hello,
reading your symptoms you might have run into the same problem I'm looking at for two days now.
Can you run regression test? If its commit f124c7cc38e7edf0823347afa5f8e7126143080d ("ntdll: Simplify the thread startup routine and make it CPU-specific.") we're talking about the same thing.
In that case please provide the Linux distribution name/version/arch and the GCC version (gcc -v).
It's a (child) thread termination problem which was introduced by AJ's refactoring of i386 thread entry point wrapper.
The problem interestingly only manifests when the child thread entry point function (called by wrapper) returns non-zero exit code (passed to pthread_exit).
Libgcc's forced unwind heuristics fails on the wrapper stack layout/opcode sequences, causing segfault in unwind phase 2.
Regards