Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 3 Sep 2002 14:42:17 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: A Simple Real World Benchmark for cygwin
Message-ID: <20020903144217.C12899@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020902155542 DOT GC14051 AT redhat DOT com> <CHEDKHJJDLOCCOFLMGEAOEHMCLAA DOT dvasaru AT broadpark DOT no> <20020902220234 DOT GA22844 AT redhat DOT com> <20020903102756 DOT V12899 AT cygbert DOT vinschen DOT de> <1031045914 DOT 3d74831ad243d AT mail DOT broadpark DOT no> <20020903135135 DOT Z12899 AT cygbert DOT vinschen DOT de> <1031054399 DOT 31077 DOT 52 DOT camel AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1031054399.31077.52.camel@lifelesswks>
User-Agent: Mutt/1.3.22.1i

On Tue, Sep 03, 2002 at 09:59:57PM +1000, Robert Collins wrote:
> On Tue, 2002-09-03 at 21:51, Corinna Vinschen wrote:
> 
> > Yep, that's the problem.  And the reasoning for calling CoInit/CoUnint
> > always as pair here since there's no way to rely on that the application
> > will *not* call CoUnit somewhere in the middle of its processing.
> 
> If it does, and it didnt' call CoInit, it is an application bug, and not
> our problem. Thats why there is the requirement to pair the calls - to
> allow us to call it once when we need it, and once on shutdown. If we
> need to call it once per thread, then IMO we simply set a per-thread
> flag when we have called it.

That's not the point.  The application *may* call CoInit() before
requesting the first path to a shortcut and it *may* call CoUninit()
before requesting another path to a shortcut, all in the same thread.
The CoInit/CoUnint brace in shortcut.c is safe against that:

    Application  Cygwin-DLL

    CoInit()
    lstat()    ->  CoInit()
                   CoUninit()
    CoUninit()
    lstat()    ->  CoInit()
                   CoUninit()

while storing our own state is not safe:

    Application  Cygwin-DLL

    CoInit()
                   CoInit()
    lstat()    ->  ok
    CoUninit()
    lstat()    ->  ???

To workaround that situation, Cygwin would have to call CoInit()
anyway to know it's state.  Since that requires to be balanced
according to MSDN...

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/