On Tue, Jul 15, 2014 at 08:40:32PM +0000, Nellis, Kenneth wrote: >From: Christopher Faylor >>On Tue, Jul 15, 2014 at 07:17:48PM +0000, Nellis, Kenneth wrote: >>>From: Nellis, Kenneth >>><snip> >>>> Well, I'm getting different results with the latest snapshot. >>>> Instead of getting the error message, I'm getting a hang for maybe a >>>> minute before it continues. >>>> >>>> I used the following command to encourage a failure: >>>> >>>> clear; for f in $(find */Debug -name '*Subsystem'); do echo === $f >>>> ===; strings $f | grep '\.cpp$' | sort | uniq -c | sort -n; done >>><snip> >>> >>>Thought it might be useful to add that I can fairly easily get the same >>>minute-long hang with a simpler command: >>> >>>Cygwin64> strings *Subsystem | wc -l >> >>What's your cwd when you run this command? > >Well, it *was* on a network drive, but that appears to be irrelevant: > >Cygwin64> date; seq 10000 | wc -l; date >Tue Jul 15 16:31:52 EDT 2014 >10000 >Tue Jul 15 16:32:52 EDT 2014 >Cygwin64> pwd >/home/knellis >Cygwin64> cygpath -w $PWD >C:\cygwin\home\knellis >Cygwin64> uname -srvmo >CYGWIN_NT-6.1 1.7.31s(0.273/5/3) 20140715 15:34:37 x86_64 Cygwin >Cygwin64>
Yes, I saw that, but I can't duplicate the problem with that command sequence. 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
