Re: Zsh 3.1.6 still hangs on for loops utilizing lots of stdout

[Clint Olsen <olsenc@ichips.intel.com>]

I went ahead and ran with set -x.  It is failing in the middle of one of
the cats (no meow):

...
+/afs/pdx/proj/otools/bin/AIX/zsh:8> cat x_0m0fm00pm_d_m4_250.char_summary
+/afs/pdx/proj/otools/bin/AIX/zsh:6> read file
+/afs/pdx/proj/otools/bin/AIX/zsh:8> cat x_0m0fm00pm_d_m4_350.char_summary
+/afs/pdx/proj/otools/bin/AIX/zsh:6> read file
+/afs/pdx/proj/otools/bin/AIX/zsh:8> cat x_0m0fm01p1_d_m2_150.char_summary
+/afs/pdx/proj/otools/bin/AIX/zsh:6> read file
+/afs/pdx/proj/otools/bin/AIX/zsh:8> cat x_0m0fm01p1_d_m4_250.char_summary

The shell hangs.  ^Z nor ^C cause it to return a prompt.

-Clint

On Feb 03, Bart Schaefer wrote:
> On Feb 3, 10:45am, Clint Olsen wrote:
> > Subject: Zsh 3.1.6 still hangs on for loops utilizing lots of stdout
> >
> > for file in *.something
> > do
> >   cat $file
> > done > /tmp/concat
> 
> Have you tried doing this with "set -x" (aka "setopt xtrace") in effect?
> You should then get one line written to standard error for each "cat"
> that executes.  This may help narrow down where the failure is.
> 
> You're certain that none of the *.something files is a named pipe or
> other device special file?  What does "ps" say the state of the process
> is at the time that it hangs?  (I.e., you're sure the process isn't in
> state D, disk wait?)