Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <01C0FE95.54BB7F10.jorgens@coho.net> From: Steve Jorgensen Reply-To: "jorgens@coho.net" To: "Cygwin List (E-mail)" Subject: RE: pthreads works, sorta Date: Tue, 26 Jun 2001 23:11:27 -0700 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit OK, I'm over my head to even try to participate in this, but it seems to me that if you want to check for the condition where you can neither read nor write, and you can never write if you can't read, then you only need to check the read condition. You only need to check the write condition if you need to distinguish between read-only and read/write. -----Original Message----- From: Robert Collins [SMTP:robert.collins@itdomain.com.au] Sent: Tuesday, June 26, 2001 10:49 PM To: Tak Ota; cygwin@cygwin.com Subject: RE: pthreads works, sorta > -----Original Message----- > From: Tak Ota [mailto:Takaaki.Ota@am.sony.com] > Sent: Wednesday, June 27, 2001 3:53 PM > To: cygwin@cygwin.com > Subject: Re: pthreads works, sorta > > > I'm not sure either. If that is the case, replacing IsBadWritePtr > with IsBadReadPtr maybe the answer since can't read mans can't write. > Nope, write is the one :] IIRC my cpu bits correctly there is a page bit for readonly, not page bits for read and for write. So writeable implies readable, readable does not imply writeable. 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/ -- 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/