DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=kN6yWaohqDc073lzc3c2qKcAlA8Id
	7fiMvLKqe4ZGGDgu95ZIinTyFi7Zje0oQTXTzfiTSJsa2UCrQtVnJl2XRAKwVjgt
	ZullsRuqFVYJ4XHso/yvmW+NcyCG6BDxOR/pmLt3vUbmPjg0x+YDoiltqb6oGH8B
	pMkeQ5C0PHOmQQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: David Conrad <DavidConrad@acm.org>
Date: Sat, 19 May 2018 23:26:17 -0400
Message-ID: <CAEotdwnTihdr7AdRFNWyvPvtxP57YjZXfgWy__X2JSpfkiwB8Q@mail.gmail.com>
Subject: Re: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
To: cygwin mailing list <cygwin@cygwin.com>
Content-Type: text/plain; charset="UTF-8"

On Thu, May 17, 2018 at 01:54 PM, L A Walsh <cygwin@tlinx.org> wrote:
> Very wierd.  It triggers so fast, and whatever is causing it, likely
> happens on a probe by 'ls' before ls even displays any output.
>
> I 'can' go into the same directory and do a "echo *" (or better,
> printf "%s\n" *  --- and that doesn't trigger it.
>
> I think I also triggered it once with 'tree'.  Very annoying.
>

You could try writing a small C program that does a readdir of that
directory and lstat of each file in it, logging what it's about to do
before each step. That would let you narrow down which entry is
triggering it, if that is indeed the cause.

I think Michel LaBarre's suggestion of running chkdsk and sfc is a
good one; strace also might help.

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