From: Alexandre Duret-Lutz <duret_g@epita.fr>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk, 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 17:11:07 +0100 [thread overview]
Message-ID: <mvbematq76s.fsf@phobos.lrde.epita.fr> (raw)
In-Reply-To: Sven Wischnowsky's message of "Fri, 4 Feb 2000 13:30:53 +0100 (MET)"
>>> "Sven" == Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
Sven> Alexandre Duret-Lutz wrote:
[...]
>> for i in *.wav
>> do
>> 8hz-mp3 $i $i:r.mp3
>> done
[...]
Sven> Well, we had some problems with IO and AIX but this stack trace looks
Sven> completely fine -- saying only that it's waiting for the 8hz-mp3.
Indeed. In fact zsh was still running and the loop finished: 8hz's work
was done on each file.
Sven> In both cases: does it happen with other shells, too?
Yes! Maybe there is something wrong,
In the two cases below, I run the loop in the launched rxvt.
And that rxvt which is segfaulting.
/goinfre/swiss-1 % gdbterm zsh 11:27 #14
/home/prolob/pollux/mbin/gdbterm: line 2: 6751 Segmentation fault rxvt +ls +sb -title GDBterm -e sh -c 'exec rxvt +ls +sb -e gdb --tty=`tty` '"$*"
/goinfre/swiss-1 % rxvt -e bash Err 139 #15
zsh: segmentation fault rxvt -e bash
with another terminal emulator (xterm), this behave differently:
after a few iterations in the for loop, it's like something is going mad
and print newlines in loop. I tried to run the whole loop
through `od' to see if these where realy newlines or something else :
/goinfre/swiss-2 % for i in *.wav Err 139 #6
do
8hz-mp3 $i $i:r.mp3
done | od
[...lot's of output...]
zsh: exit 141 for i in *.wav; do; 8hz-mp3 $i $i:r.mp3; done | od |
zsh: segmentation fault od
How fun! now, that's od which is segfaulting. BTW where does this last pipe
(after `od' on the exit report line) come from?.
I will try to see if I can reproduce this without 8hz.
--
Alexandre Duret-Lutz
next prev parent reply other threads:[~2000-02-04 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 12:30 Sven Wischnowsky
2000-02-04 16:11 ` Alexandre Duret-Lutz [this message]
-- 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=mvbematq76s.fsf@phobos.lrde.epita.fr \
--to=duret_g@epita.fr \
--cc=olsenc@ichips.intel.com \
--cc=wischnow@informatik.hu-berlin.de \
--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).