X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org X-USANET-Source: 165.212.120.254 IN aeolus AT electric-cloud DOT com s1hub1.EXCHPROD.USA.NET X-USANET-MsgId: XID739oiBXGj0450Xo2 From: John Carey To: "cygwin AT cygwin DOT com" Date: Thu, 2 Sep 2010 23:32:29 +0000 Subject: RE: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set Message-ID: <3C031C390CBF1E4A8CE1F74DE7ECAF3A158EDA702A@MBX8.EXCHPROD.USA.NET> References: <3C031C390CBF1E4A8CE1F74DE7ECAF3A140684F0AA AT MBX8 DOT EXCHPROD DOT USA DOT NET> <20100811084926 DOT GC26152 AT calimero DOT vinschen DOT de> <3C031C390CBF1E4A8CE1F74DE7ECAF3A140684F0B0 AT MBX8 DOT EXCHPROD DOT USA DOT NET> ,<20100812081151 DOT GT14202 AT calimero DOT vinschen DOT de> In-Reply-To: <20100812081151.GT14202@calimero.vinschen.de> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Aug 12 01:11, Corinna Vinschen wrote: > On Aug 12 06:54, Andy Koppe wrote: > > On 11 August 2010 20:55, John Carey wrote: > > > So is your idea that if SetCurrentDirectory() fails because > > > of path length or permissions, then Cygwin would just accept > > > the failure and keep an internal record the > > > POSIX current working directory and use that for all > > > Cygwin calls, not the Win32 notion of current directory? > > > > Yes. The question then becomes what to do about the Win32 working > > directory in that case. >=20 > Actually, Cygwin accepts *any* directory it can open as CWD: >=20 > - Directories which can only be opened under SE_BACKUP_NAME. > - Directories with a length up to 32768 chars. > - Virtual directories, which don't exist at all as filesystem-based > paths, like /proc, /cygdrive, etc. >=20 In Aug 17 10:15, Corinna Vinschen wrote: > I just released 1.7.6-1. ... > What changed since Cygwin 1.7.5: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D >=20 > - Cygwin handles the current working directory entirely on its own. The > Win32 current working directory is set to an invalid path to be out of > the way. This affects calls to the Win32 file API (CreateFile, etc.). > See http://cygwin.com/htdocs/cygwin-ug-net/using.html#pathnames-win32-a= pi Thank you very much for the fix! I've been running tests against Cygwin 1.7.6, and then 1.7.7, and those sporadic, non-deterministic failures in CreatePipe did stop after the 1.7.6 upgrade, and are still gone in 1.7.7. I think it's been long enough to conclude that it is not just the non-determinism--it really is fixed, as expected. I understand that this issue opened a can of worms; thanks again for your efforts to overcome those difficulties. -- John -- 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