This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.5.25-15: pthread_join deadlocks


On Fri, Nov 20, 2009 at 09:01:00AM -0500, Charles Wilson wrote:
>Ryan Johnson wrote:
>> Out of curiosity, how much did removing the racy optimization hurt
>> performance? The patch just yanked it completely iirc. An alternative
>> might be to have the main thread check for single-thread environment
>> only at acquire time, and then release only if it acquired (the latter
>> is probably a good idea regardles...).
>
>The problem is, IIRC there is no such thing as a single-thread
>environment for cygwin programs: every cygwin program has a secondary
>thread that handles translating certain windows events into unixy
>signals, or something like that. I think.

Yes, there's at least one extra thread active in every cygwin program.
If you've used select() at any point there will be more.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]