From: Timothy Miller <tsm@cs.brown.edu>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: fatal flaw zsh 4.0.1 on irix 6.3 & 6.5: suspend "ls -l|less" then resume hangs
Date: 30 Jul 2001 16:18:02 -0400 [thread overview]
Message-ID: <yehhevugohx.fsf@water.cs.brown.edu> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Thu, 12 Jul 2001 03:39:07 +0000"
On Thu, 12 Jul 2001 03:39:07 +0000, "Bart Schaefer" <schaefer@candle.brasslantern.com> wrote:
> Yes, there was at least one other bug fix after -pws-3:
>
> * Sven: 9345: Src/exec.c, Src/jobs.c, Src/zsh.h:
> bug with job control when group leader exits; other problems
> with subshells.
>
> So it would be more helpful to see the `ps' output for 4.0.2 (say) than
> for 3.1.6-pws-3.
4.0.2 zsh +Z -f, ps -fljt ttyq4 with irrelevant procs removed:
initial prompt
F S UID PID PPID PGID SID C PRI NI P SZ:RSS WCHAN STIME TTY TIME CMD
b0 S tsm 8561 915 8561 915 5 28 20 * 593:218 8039e0b0 16:02:16 ttyq4 0:00 ./Src/zsh +Z -f
ls -lR /|cat running
b0 S tsm 8564 8561 8564 915 3 61 20 * 45:25 c0d1261c 16:02:54 ttyq4 0:00 cat
b0 S tsm 8561 915 8561 915 0 39 20 * 609:232 8039d510 16:02:16 ttyq4 0:00 ./Src/zsh +Z -f
b8 S tsm 8563 8561 8563 915 24 20 20 * 394:114 803fe164 16:02:54 ttyq4 0:00 ls -lR /
after ^Z
b0 T tsm 8564 8561 8564 915 0 60 20 * 45:25 - 16:02:54 ttyq4 0:00 cat
b0 S tsm 8561 915 8561 915 0 39 20 * 609:233 8039d510 16:02:16 ttyq4 0:00 ./Src/zsh +Z -f
b0 S tsm 8563 8561 8563 915 0 60 20 * 394:114 c0d12620 16:02:54 ttyq4 0:01 ls -lR /
At this point it's hung. Actually, on examining the mail I sent when I first
tried the |cat (Jun 12) it had the same hang-on-first-suspend, which I had
forgotten, so it's not different behavior after all.
> However, I note that in -pws-2, both `cat' and `ls' are in the same pgrp
> but it is `ls' that is stopped. Did you try either of the patches that
> Sven sent?
Yes, and even sent out a reply (Jul 6): separately or together, they didn't
affect the problem. ps outputs (which I didn't include originally) follow. I
am assuming, by the way, that the only thing I need to do after applying the
patch is type "make".
first patch only:
initial prompt
b0 S tsm 8684 915 8684 915 0 28 20 * 593:218 8039e0b0 16:09:37 ttyq4 0:00 ./Src/zsh +Z -f
ls -lR /|cat running
b8 R tsm 8686 8684 8686 915 29 20 20 * 394:114 - 16:09:51 ttyq4 0:00 ls -lR /
b0 S tsm 8687 8684 8687 915 1 60 20 * 45:25 c0d1261c 16:09:51 ttyq4 0:00 cat
b0 S tsm 8684 915 8684 915 0 39 20 * 609:232 8039d510 16:09:37 ttyq4 0:00 ./Src/zsh +Z -f
after ^Z
b0 S tsm 8686 8684 8686 915 0 60 20 * 394:114 c0d12620 16:09:51 ttyq4 0:01 ls -lR /
b0 T tsm 8687 8684 8687 915 0 60 20 * 45:25 - 16:09:51 ttyq4 0:00 cat
b0 S tsm 8684 915 8684 915 0 39 20 * 609:233 8039d510 16:09:37 ttyq4 0:00 ./Src/zsh +Z -f
It's now hung.
-----
both first and second patches:
initial prompt
b0 S tsm 8752 915 8752 915 0 28 20 * 593:219 8039e0b0 16:12:10 ttyq4 0:00 ./Src/zsh +Z -f
running
b0 S tsm 8752 915 8752 915 0 39 20 * 609:233 8039d510 16:12:10 ttyq4 0:00 ./Src/zsh +Z -f
b0 R tsm 8754 8752 8754 915 30 75 20 * 394:114 - 16:12:31 ttyq4 0:01 ls -lR /
b0 S tsm 8755 8752 8755 915 2 61 20 * 45:25 c0d1261c 16:12:31 ttyq4 0:00 cat
^Z
b0 S tsm 8752 915 8752 915 0 39 20 * 609:234 8039d510 16:12:10 ttyq4 0:00 ./Src/zsh +Z -f
b0 S tsm 8754 8752 8754 915 0 60 20 * 394:114 c0d12620 16:12:31 ttyq4 0:01 ls -lR /
b0 T tsm 8755 8752 8755 915 0 60 20 * 45:25 - 16:12:31 ttyq4 0:00 cat
hung
-----
second patch only:
initial prompt
b0 S tsm 8819 915 8819 915 0 28 20 * 593:219 8039e0b0 16:14:23 ttyq4 0:00 ./Src/zsh +Z -f
running
b0 S tsm 8822 8819 8822 915 1 60 20 * 45:25 c0d1261c 16:14:35 ttyq4 0:00 cat
b0 S tsm 8819 915 8819 915 0 39 20 * 609:233 8039d510 16:14:23 ttyq4 0:00 ./Src/zsh +Z -f
b0 R tsm 8821 8819 8821 915 39 79 20 * 394:114 - 16:14:35 ttyq4 0:00 ls -lR /
^Z
b0 T tsm 8822 8819 8822 915 0 60 20 * 45:25 - 16:14:35 ttyq4 0:00 cat
b0 S tsm 8819 915 8819 915 0 39 20 * 609:234 8039d510 16:14:23 ttyq4 0:00 ./Src/zsh +Z -f
b0 S tsm 8821 8819 8821 915 0 60 20 * 394:114 c0d12620 16:14:35 ttyq4 0:01 ls -lR /
hung
Tim
next prev parent reply other threads:[~2001-07-30 20:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 15:11 Timothy Miller
2001-06-12 8:15 ` Sven Wischnowsky
2001-06-12 15:00 ` Timothy Miller
[not found] ` <1010612154026.ZM24394@candle.brasslantern.com>
2001-06-12 16:13 ` Timothy Miller
2001-06-13 3:55 ` Bart Schaefer
2001-07-06 22:40 ` Timothy Miller
2001-06-14 7:32 ` Sven Wischnowsky
2001-07-06 22:52 ` Timothy Miller
2001-07-10 15:22 ` Timothy Miller
2001-07-10 16:25 ` Bart Schaefer
2001-07-10 21:26 ` Timothy Miller
2001-07-10 23:27 ` Bart Schaefer
2001-07-11 8:33 ` Sven Wischnowsky
2001-07-11 9:51 ` Sven Wischnowsky
2001-07-11 18:59 ` Timothy Miller
2001-07-12 3:39 ` Bart Schaefer
2001-07-30 20:18 ` Timothy Miller [this message]
2001-07-30 21:24 ` Bart Schaefer
2001-07-30 22:08 ` Timothy Miller
2001-07-31 8:20 ` Sven Wischnowsky
2001-07-31 8:30 ` Borsenkow Andrej
2001-07-31 14:35 ` Timothy Miller
2001-07-31 20:50 ` Timothy Miller
2001-08-01 8:35 ` Sven Wischnowsky
2002-02-25 9:31 ` 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=yehhevugohx.fsf@water.cs.brown.edu \
--to=tsm@cs.brown.edu \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.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).