From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Cc: Clint Olsen <olsenc@ichips.intel.com>
Subject: Re: Zsh 3.1.6 still hangs on for loops utilizing lots of stdout
Date: Fri, 4 Feb 2000 13:30:53 +0100 (MET) [thread overview]
Message-ID: <200002041230.NAA24341@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Alexandre Duret-Lutz's message of 04 Feb 2000 10:24:30 +0100
Alexandre Duret-Lutz wrote:
> >>> "Clint" == Clint Olsen <olsenc@ichips.intel.com> writes:
>
> [...]
>
> Clint> for file in *.something
> Clint> do
> Clint> cat $file
> Clint> done > /tmp/concat
>
> Clint> The number of files matched were probably in the thousand or so
> Clint> range, each with about 10 lines of data. Zsh hangs on large jobs
> Clint> like this to the point of having to kill the window entirely (^C
> Clint> doesn't work, neither does ^Z).
I've tried it now under DU and Linux but can't reproduce it. I can
understand that it is hard (even seemingly impossible) to stop such a
loop with ^Z because you have to hit one of the cats (and then those
animal-rights people will get you and... er, no), which can be
difficult if they finish very quickly. However, ^C should work even
then -- and it does for me.
We had some patches for the execution, jobs and signal code but most
of them were before the 3.1.6 release and I don't think any of those
that came afterwards should have changed this.
Hm, don't have an idea how this can happen.
> I have seen this on linux too (and attributed to
> my kernel, wich is making `Oops' sometimes...)
> when making a loop of the form :
>
> for i in *.wav
> do
> 8hz-mp3 $i $i:r.mp3
> done
>
> *.wav did match only about 20 files, and the xterm disapeared
> after the second or third file processed. Although the xterm
> is dead, zsh and 8hz are still alive (but waiting) :
>
> PID PPID WCHAN COMMAND
> 3533 6548 signal zsh
> 3587 3533 down_f 8hz-mp3 audio_12.wav audio_12.mp3
>
> (I never saw that `down_f' flag before)
>
> If I attach to 3533 to see where it wait I see
>
> (gdb) bt
> #0 0x400ad8fa in sigsuspend () from /lib/libc.so.6
> ...
>
> Don't know if it can help.
>
> (And since you are guessing it maybe related to stdout output, I must
> state that 8hz is quite verbose too).
Well, we had some problems with IO and AIX but this stack trace looks
completely fine -- saying only that it's waiting for the 8hz-mp3.
In both cases: does it happen with other shells, too?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-02-04 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 12:30 Sven Wischnowsky [this message]
2000-02-04 16:11 ` Alexandre Duret-Lutz
-- strict thread matches above, loose matches on Subject: below --
2000-02-18 9:44 Sven Wischnowsky
2000-02-17 9:20 Sven Wischnowsky
2000-02-17 17:18 ` Bart Schaefer
2000-02-07 10:15 Sven Wischnowsky
2000-02-03 18:45 Clint Olsen
2000-02-04 9:24 ` Alexandre Duret-Lutz
[not found] ` <000203162102.ZM8092@candle.brasslantern.com>
2000-02-16 19:08 ` Clint Olsen
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=200002041230.NAA24341@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=olsenc@ichips.intel.com \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).