zsh-workers
 help / color / mirror / code / Atom feed
From: Alexandre Duret-Lutz <duret_g@epita.fr>
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: 04 Feb 2000 10:24:30 +0100	[thread overview]
Message-ID: <mvbwvolqq0h.fsf@phobos.lrde.epita.fr> (raw)
In-Reply-To: Clint Olsen's message of "Thu, 3 Feb 2000 10:45:48 -0800"

>>> "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 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
#1  0x80991bc in signal_suspend (sig=17, sig2=0)
    at ../../last/Src/signals.c:343
#2  0x8077e03 in waitjob (job=2, sig=0) at ../../last/Src/jobs.c:886
#3  0x8077f57 in waitjobs () at ../../last/Src/jobs.c:916
#4  0x805eabe in execpline (state=0xbffff6d0, slcode=2562, how=18, last1=0)
    at ../../last/Src/exec.c:986
#5  0x805e0b9 in execlist (state=0xbffff6d0, dont_change_job=1, exiting=0)
    at ../../last/Src/exec.c:766
#6  0x807dd1e in execfor (state=0xbffff6d0, do_exec=0)
    at ../../last/Src/loop.c:134
#7  0x806240e in execcmd (state=0xbffff6d0, input=0, output=0, how=18, last1=2)
    at ../../last/Src/exec.c:2109
#8  0x805f39b in execpline2 (state=0xbffff6d0, pcode=131, how=18, input=0, 
    output=0, last1=0) at ../../last/Src/exec.c:1119
#9  0x805e682 in execpline (state=0xbffff6d0, slcode=6146, how=18, last1=0)
    at ../../last/Src/exec.c:915
#10 0x805e0b9 in execlist (state=0xbffff6d0, dont_change_job=0, exiting=0)
    at ../../last/Src/exec.c:766
#11 0x805df66 in execode (p=0x40015278, dont_change_job=0, exiting=0)
    at ../../last/Src/exec.c:712
#12 0x8072a3d in loop (toplevel=1, justonce=0) at ../../last/Src/init.c:150
#13 0x805138c in main (argc=1, argv=0xbffff7c4) at ../../last/Src/main.c:89

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).

[...]

-- 
Alexandre Duret-Lutz


  reply	other threads:[~2000-02-04  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-03 18:45 Clint Olsen
2000-02-04  9:24 ` Alexandre Duret-Lutz [this message]
     [not found] ` <000203162102.ZM8092@candle.brasslantern.com>
2000-02-16 19:08   ` Clint Olsen
2000-02-04 12:30 Sven Wischnowsky
2000-02-04 16:11 ` Alexandre Duret-Lutz
2000-02-07 10:15 Sven Wischnowsky
2000-02-17  9:20 Sven Wischnowsky
2000-02-17 17:18 ` Bart Schaefer
2000-02-18  9:44 Sven Wischnowsky

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=mvbwvolqq0h.fsf@phobos.lrde.epita.fr \
    --to=duret_g@epita.fr \
    --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).