zsh-workers
 help / color / mirror / code / Atom feed
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: 12 Jun 2001 12:13:26 -0400	[thread overview]
Message-ID: <yehu21lk76h.fsf@water.cs.brown.edu> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Tue, 12 Jun 2001 15:40:26 +0000"

On Tue, 12 Jun 2001 15:40:26 +0000, "Bart Schaefer" <schaefer@candle.brasslantern.com> wrote:
> On Jun 12, 11:00am, Timothy Miller wrote:
> }
> } I can't type fast enough to suspend cat before it exits!
> 
> Use "ls -lR / | cat" and I bet you'll have time.

Yes, I thought of something like that shortly after I sent the email...what
comes of sending too rapidly...anyway, if I do that, it hangs on the first
suspend.

irix 6.3, zsh 4.0.1 -f,  ls -lR /|cat, then suspend:

  F S      UID   PID  PPID  PGID   SID  C PRI NI  P    SZ:RSS      WCHAN    STIME TTY     TIME CMD
 b0 S      tsm 13962 13961 13962 13905  0  60 20  *   394:114   c06afbc0 11:55:29 ttyq13  0:01 ls -lR / 
 b0 T      tsm 13963 13961 13963 13905  0  60 20  *    45:25           - 11:55:29 ttyq13  0:00 cat 
 b0 S      tsm 13961 13905 13961 13905  0  39 20  *   732:297   8039d510 11:55:26 ttyq13  0:00 zsh-4.0.1 -f 

zsh asleep syscall 166, all sigs held but 1, 9, 18, 23
ls asleep on syscall 5, no sigs held/pending
cat stopped, no sigs held/pending

just found more authoritative info on syscall numbers; syscall 4 is read(),
syscall 5 is write(), syscall 166 is sigsuspend(), which makes much more
sense.
   Tim


  parent reply	other threads:[~2001-06-12 16:14 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 [this message]
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
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=yehu21lk76h.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).