Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Subject: RE: pthreads works, sorta MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 27 Jun 2001 15:32:03 +1000 Message-ID: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: pthreads works, sorta Thread-Index: AcD+yS0CQMxphXMVSdetc62gn97W0wAAAz4Q From: "Robert Collins" To: "Ross Smith" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id BAA31587 > -----Original Message----- > From: Ross Smith [mailto:ross DOT s AT ihug DOT co DOT nz] > Sent: Wednesday, June 27, 2001 3:31 PM > To: cygwin AT cygwin DOT com > Subject: Re: pthreads works, sorta > > > Robert Collins wrote: > > > > What does all this mean? We need to catch invalid memroy access, > > Why? A program that passes an invalid thread handle is broken. > Penalising non-broken programs merely to provide better error checking > for broken ones doesn't sound reasonable to me. > Even though the POSIX behaviour is undefined for passed invalid thread variables, cygwin1.dll locking up is not a pretty way to handle failure. However, I'll consider removing the checks for non-debug builds of cygwin, but _only_ once the in-cygwin code is considered stable and complete. Until then I'm leery of having a no-check environment. Still I've found what seems to be a good alternative function that is _much_ faster, and still provides the reliability I was looking for. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/