From: David Conrad <DavidConrad@acm.org>
To: cygwin mailing list <cygwin@cygwin.com>
Subject: Re: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
Date: Sun, 20 May 2018 11:37:00 -0000 [thread overview]
Message-ID: <CAEotdwnTihdr7AdRFNWyvPvtxP57YjZXfgWy__X2JSpfkiwB8Q@mail.gmail.com> (raw)
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
next reply other threads:[~2018-05-20 3:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-20 11:37 David Conrad [this message]
2018-05-21 20:18 ` L A Walsh
2018-05-22 2:07 ` Michel LaBarre
2018-05-22 10:48 ` L A Walsh
2018-05-23 20:13 ` Andrey Repin
2018-05-25 3:25 ` L A Walsh
2018-05-25 14:56 ` Andrey Repin
-- strict thread matches above, loose matches on Subject: below --
2018-05-15 12:58 L A Walsh
[not found] ` <000a01d3ec54$a2bb2ca0$e83185e0$@rogers.com>
2018-05-15 16:51 ` L A Walsh
2018-05-15 17:18 ` James Darnley
[not found] ` <2b3cf1ed-1a3f-d8ff-136b-0ee533ae9e59@wagner.is>
2018-05-15 19:54 ` L A Walsh
2018-05-16 17:26 ` Andrey Repin
2018-05-17 13:22 ` L A Walsh
2018-05-17 19:41 ` Brian Inglis
2018-05-17 20:38 ` L A Walsh
2018-05-17 22:09 ` Michel LaBarre
2018-05-18 4:49 ` L A Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEotdwnTihdr7AdRFNWyvPvtxP57YjZXfgWy__X2JSpfkiwB8Q@mail.gmail.com \
--to=davidconrad@acm.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).