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 Date: Wed, 27 Jun 2001 02:31:28 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: pthreads works, sorta Message-ID: <20010627023128.R19058@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <030b01c0fed5$afbfddd0$c9823bd5@dima> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <030b01c0fed5$afbfddd0$c9823bd5@dima>; from dmitry@baikal.ru on Wed, Jun 27, 2001 at 02:51:13PM +0800 On Wed, Jun 27, 2001 at 02:51:13PM +0800, Dmitry Timoshkov wrote: >"Robert Collins" wrote: > >[skipped] > >> What does all this mean? We need to catch invalid memroy access, and >> ValidQuery was supplied by Chris as a tool to do that. > >In a multithreaded environment VirtualQuery, IsBad* and similar approaches >are wrong. It can't be guaranteed that after a successful test that memory >will be still accessable. They are not necessarily wrong if they are controlled by appropriate mutexes. The file handling code should be protected this way. I don't know about the thread code, though. cgf -- 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/