X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 13 Jan 2010 10:59:07 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	volunteer solicited (was Re: Possible BSOD from getcwd on WinXP SP3)
Message-ID:	<20100113155907.GB32366@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<D79FE0983947DC4FA436B4B76CBCCD9B075DEF61 AT AMEDMLNARMC137 DOT amed DOT ds DOT army DOT mil> <4B4DED28 DOT 5070808 AT gmx DOT de>
MIME-Version:	1.0
In-Reply-To:	<4B4DED28.5070808@gmx.de>
User-Agent:	Mutt/1.5.20 (2009-06-14)
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

On Wed, Jan 13, 2010 at 04:56:24PM +0100, Matthias Andree wrote:
>Am 13.01.2010 16:18, schrieb Henson, George A CTR USA MEDCOM JMLFDC:
>> A very deep directory tree called conftest3
>> (conftest3/conftest3/conftest3/...)
>> The source for conftest (conftest.c - attached)
>> Compiled binary contest.exe
>> 
>> In Cygwin attempting to cd to the bottom of the conftest3 directory tree
>> will yield a BSOD. Running conftest.exe will yield a BSOD. A little
>> experimentation with conftest.c shows the error happens during the
>> creation of the directory tree. The Windows native tools are unable to
>> correctly manage the conftest3 tree (I cannot remove it or descend to
>> the bottom)
>> 
>> The only information I have been able to get out of the Windows crash
>> dumps is the fault happens somewhere in the ntfs.sys driver.
>
>Might this be simple filesystem corruption?
>If so, chkdsk might be your friend - give it a spin.

I think we need a BSOD FAQ entry.  Anyone want to write one?

cgf

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