Re: Another (simpler) bash scripting question...

[Michael O'Donnell]

Dang it!  I may coincidentally have just found a fairly profound
bash bug related to usage of that "spew | while read" idiom.

Here's what I do to cause bash to say "Segmentation fault"

   cd /
   find . -type f | while read f
   do
       ls -laFd $f
   done


Collecting the list in a file first doesn't help:

   find . -type f >/tmp/fileList
   cat /tmp/fileList | while read f
   ...etc, etc

bash has to crank through a LOT of files before it
chokes, but it always chokes, and it appears not to
depend on the actual input.  BTW (and this is probably
a red herring) it seems usually to choke after it's
cranked through approx 32000 files, which is in the
neigborhood of one of those Suspicious Powers Of Two(tm)

I'm running the "testing" release of Debian with
a 2.4.18 kernel and bash 2.05a.0(1)-release

Investigation continues...


*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************