Christopher Faylor wrote: > This isn't a bug in Cygwin.
I've never made a statement that it is. It's just an unexpected and undesired behaviour I wanted to get rid of. The context was there to make it clear what exactly is happening on that particular control flow path. > Your takeaway from this is: > > 1) I don't care about this. Not suspending the "sig" thread fixes my > problem. Yes, it does. And since when it happens, the program is about to die anyway, I don't think that tracking its exact causes is worth of my effort. > We try hard not to call SuspendThread when the program is in the middle of > a Windows call. I don't use the function either, except when under abnormal circumstances, when I have the very last chance to report a problem. Piotr -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
