This is the mail archive of the cygwin-patches@cygwin.com 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: [PATCH] added locks in pthread code



> -----Original Message-----
> From: cygwin-patches-owner@cygwin.com 
> [mailto:cygwin-patches-owner@cygwin.com] On Behalf Of Robert Collins
> Sent: Monday, 10 June 2002 6:41 PM
> To: 'Thomas Pfaff'
> Cc: cygwin-patches@cygwin.com
> Subject: RE: [PATCH] added locks in pthread code
> 
> 
> 
> 
> > -----Original Message-----
> > From: Thomas Pfaff [mailto:tpfaff@gmx.net] 
> > Sent: Monday, 10 June 2002 4:48 PM
> > To: Robert Collins
> > Cc: cygwin-patches@cygwin.com
> > Subject: RE: [PATCH] added locks in pthread code
> > 
> > 
> > 
> > I wanted to make sure that a thread can not be cancelled 
> > asynchronous when
> > it is in the cleanup push call, but i think it could be done 
> > better with
> > InterlockedExchangePointer.
> 
> Yes. Look at the destructor code, or the pthread_atfork list code -
> there is a thread safe list based around InterlockedExchangePointer.

Or, call setcancelstate twice during your pthread_cleanup_push macro.
Once to set PTHREAD_CANCEL_ENABLE, and once to restore the old value.
That avoids the issue completely, and is in spec with P1003.1.

Rob


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