X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Chuck <skilover AT bluebottle DOT com>
Subject:	Re: Help. Cygwin corrupting files
Date:	Mon, 12 Feb 2007 13:21:31 -0500
Lines:	33
Message-ID:	<eqqb7c$rg$1@sea.gmane.org>
References:	<eqik0d$df7$1 AT sea DOT gmane DOT org> <45CCDE32 DOT 60108 AT cygwin DOT com> <eqq3ov$tv8$2 AT sea DOT gmane DOT org> <45D09619 DOT 8 AT cygwin DOT com>
Mime-Version:	1.0
User-Agent:	Thunderbird 1.5.0.9 (Windows/20061207)
In-Reply-To:	<45D09619.8@cygwin.com>
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

Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>>> Have you checked if you can do similar operations with DOS commands?  I
>>> believe what you're seeing here is a hardware (probably disk) problem.
>>> Years ago I had a failing disk pick off files randomly for a while until
>>> the whole thing finally went.
>>>
>>>
>>
>> Is there a way to run the "ls" command in debug mode so I can see
>> exactly where it's failing? It might give me some indication of what's
>> going on.
> 
> In Cygwin, there's strace to get a look at the system calls made by
> Cygwin tools.  There's also file and process monitors from sysinternals
> (now MS) that can provide some insight.
> 

Thanks.  Can you or anyone help debugging the trace output?

I ran with strace like this:

strace -o ls2.trc -m debug ls -1

I captured output for a failed execution to ls.trc and a succesful one
to ls2.trc. ls2.trc contains about 250 lines. ls.trc contains only 1 line
	"[main] ls 1792 set_myself: myself->dwProcessId 1792"

The 2nd line in the succesful trace (ls2) is a call to
etEnvironmentStrings. Does that mean that's where it's failing when it
fails?



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

- Raw text -