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: 06 Jul 2001 18:40:04 -0400	[thread overview]
Message-ID: <yehhewplm0r.fsf@water.cs.brown.edu> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Wed, 13 Jun 2001 03:55:22 +0000"

On Wed, 13 Jun 2001 03:55:22 +0000, "Bart Schaefer" <schaefer@candle.brasslantern.com> wrote:
> On Jun 12, 12:13pm, Timothy Miller wrote:
> } Subject: Re: fatal flaw zsh 4.0.1 on irix 6.3 & 6.5: suspend "ls -l|less" 
> }
> } 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.
> 
> What output do you get from `egrep 'BROKEN|SIG' config.h` ?

I've now switched to zsh-4.0.2 for the irix debugging process, since it came
out before I had a chance to look at it again and since I get the same
problem with suspending. This is the output I get:

#define RETSIGTYPE void
/* #undef STAT_MACROS_BROKEN */
/* #undef BROKEN_SIGNED_TO_UNSIGNED_CASTING */
#define POSIX_SIGNALS 1
/* #undef BSD_SIGNALS */
/* #undef SYSV_SIGNALS */
/* #undef NO_SIGNAL_BLOCKING */
/* #undef RLIM_T_IS_UNSIGNED */
/* #undef BROKEN_KILL_ESRCH */
/* #undef BROKEN_POSIX_SIGSUSPEND */
/* #undef BROKEN_TCSETPGRP */
#define HAVE_SIGACTION 1
#define HAVE_SIGBLOCK 1
#define HAVE_SIGHOLD 1
#define HAVE_SIGNGAM 1
#define HAVE_SIGPROCMASK 1
#define HAVE_SIGRELSE 1
#define HAVE_SIGSETMASK 1


   Tim


  reply	other threads:[~2001-07-06 22:41 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 [this message]
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=yehhewplm0r.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).