Jim Meyering <[email protected]> wrote: > Aki Helin wrote: > > > [...] > > - Loop 1: 1 date > > - Loop 2: 4 dates > > - Loops 3 and 4 reading from stdin: 0 dates > > > > Machine 2, Dash, Grep 2.6.3 > > - Loop 1: 0 dates > > - Loop 2: 1 segfault (will drop core next time if this happens again) > > > > Machine 3, Bash, Grep 2.10 > > - Loop 1: 5 dates > > - Loop 2: 6 dates > > - Loop 3: 3 dates > > - Loop 4 reading from stdin: 0 dates > > Compiled with which compiler?
gcc (Debian 4.4.5-8) 4.4.5 The linker is GNU gold (GNU Binutils 2.21.1) 1.11 instead of the bundled one, but I doubt that is related. > Could it be that your Atom-based systems are sometimes too hot? Good point. One of the machines does run pretty hot at +10C above the others, but it hasn't printed any dates so far. Machine 3 above seems to be running at same temperature as the others. Doesn't seem to be temperature related, but I'm logging them now to be sure. > After 1.5 hours with zsh, and no output, I've switched to bash and dash > in separate windows (it's a 4-core x86_64 system): > bash -c 'while :; do grep RANDOM cout.sh && date; done' > dash -c 'while :; do grep RANDOM cout.sh && date; done' The intervals can be pretty long. One run (Bash and Grep 2.10) has: Thu Feb 9 00:35:59 EET 2012 Thu Feb 9 01:00:28 EET 2012 Thu Feb 9 06:35:02 EET 2012 One more data point: A date just got printed without issues even though it was matching with Grep that had been patched to crash if it tries to exit with 0 from the bottom of main(). -- Aki Helin
