Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <030b01c0fed5$afbfddd0$c9823bd5@dima>
From: "Dmitry Timoshkov" <dmitry AT baikal DOT ru>
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>,
        "Greg Smith" <gsmith AT nc DOT rr DOT com>, <cygwin AT cygwin DOT com>
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF7A0C AT itdomain002 DOT itdomain DOT net DOT au>
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" <robert DOT collins AT itdomain DOT com DOT au> 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/