X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT
X-Spam-Check-By:	sourceware.org
Date:	Wed, 18 Aug 2010 14:28:02 +0400
From:	Andrey Repin <anrdaemon AT freemail DOT ru>
Reply-To:	Andrey Repin <cygwin AT cygwin DOT com>
Message-ID:	<445852471.20100818142802@mtu-net.ru>
To:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>, cygwin AT cygwin DOT com
Subject:	Re: cygwin 1.7 lock directory problem
In-Reply-To:	<20100818085754.GP11340@calimero.vinschen.de>
References:	<AANLkTin6rup-PmQj2yCXgEBUajHhQ_J73UstwmLht-sa AT mail DOT gmail DOT com> <4C6B5191 DOT 7070602 AT cygwin DOT com> <AANLkTin8J=k9bbw7q8LTD4S7+XdT61W5fuShYdgbzf4j AT mail DOT gmail DOT com> <20100818055204 DOT GA19288 AT ednor DOT casa DOT cgf DOT cx> <20100818085754 DOT GP11340 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Greetings, Corinna Vinschen!

>> >>Do you have a series of steps that produces the problem you see?
>> >>
>> >
>> >As I said in previous mail.
>> >1. cd /cygdriver/i    ( I is mounted as a usb-stick)
>> >2.  cd /proc 3.  Use some tools such as Unlocker to check driver I,
>> >Unlocker said driver I is locked by bash.
>> >4. cd /          ( / is at d:\cygwin )
>> >5.  do the same as step 3, driver is not locked by bash.
>> 
>> That's how Cygwin 1.7.5 would work.  I would expect different behavior
>> for 1.7.6.

> No, that's also how 1.7.6 works.  I documented this behaviour in
> path.cc:

>   /* Note that we don't set the dir handle to NULL for virtual paths.
>      The handle is used to generate a stackdump file.  Since we can't
>      create a stackdump in a virtual path, we have at least *some*
>      directory handle to generate the stackdump in.

>      However, note that we have to make sure that we don't use the handle
>      wrongly as soon as we start to use it in other cases as well. */

> Looks like this behaviour is a problem and we should better close the
> old handle.  What to do with the new one?  Just set it to NULL and
> disallow stackdumps as long as we're in a virtual path?  Or set it to
> some well known path, like Cygwin's root?

/var or /tmp would be more sensible.


--
WBR,
 Andrey Repin (anrdaemon AT freemail DOT ru) 18.08.2010, <14:27>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -