X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	MailHop Outbound by DynDNS
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19V4sJlqHHMty4/mDcXgm6e
Date:	Sat, 18 Feb 2012 13:01:04 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: lstat() fails intermittently in C program -- what could cause this???
Message-ID:	<20120218180104.GB1249@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<022f01ccee48$febc6fc0$fc354f40$@vaultnow.com>
MIME-Version:	1.0
In-Reply-To:	<022f01ccee48$febc6fc0$fc354f40$@vaultnow.com>
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 Sat, Feb 18, 2012 at 07:24:14AM -0700, Leon Vanderploeg wrote:
>Greetings,
>
>I am having problems with intermittent failures of the lstat() inside a C
>program on several servers running Windows Server 2008R2.  The program
>recursively searches directories and uses lstat() to gather information on
>each file.  The files that fail most often end in .bak, but not always.
>Since the lstat() command does not return detailed failure information, I
>can't identify what is causing the failure.  Any suggestions on what might
>be causing the failures or how to gather information on what is causing the
>failure?

lstat may not return detailed error information (what UNIX program does?) but
it does return *some*.  You haven't provided enough information to help you.
If you can boil the problem down to a simple test case that is always helpful
but, barring that, at the very least, what errno is being reported?

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