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: <030b01c0fed5$afbfddd0$c9823bd5@dima> From: "Dmitry Timoshkov" To: "Robert Collins" , "Greg Smith" , References: Subject: Re: pthreads works, sorta Date: Wed, 27 Jun 2001 14:51:13 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 "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. > So the question for all the win32 gurus: > > Whats a fast way to catch (in-cygwin-dll) invalid memory access's. Can > we use structed exception handling there? Or...? Using SEH is probably a way to go. -- Dmitry. -- 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/