I understand that, and the latest version of !1088 doesn't create a new thread but instead parks aborted thread around (using an indefinite and uninterruptible `select( 0, 0, 0, 0, 0 );`) until the process fully exits.
Do you think this is still ugly, or should I pursue this lead?
My remark was actually aimed at winegstreamer and other libraries that create Unix threads. We should avoid that as far as possible.
As far as avoiding the crashes, it seems to me that now that the syscall interface is in place it should be possible to properly unwind the kernel stack.