zsh-workers
 help / color / mirror / code / Atom feed
From: Jos Backus <josb@cncdsl.com>
To: zsh-workers@sunsite.dk
Subject: Re: 4.0.1: problem with sourcing on Solaris
Date: Tue, 5 Jun 2001 14:16:19 -0700	[thread overview]
Message-ID: <20010605141619.A36532@lizzy.bugworks.com> (raw)
In-Reply-To: <1010605061126.ZM4201@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Tue, Jun 05, 2001 at 06:11:04AM +0000

Here's a clue: for some reason, after re-running configure (because I changed a
couple of entries in config.modules), BROKEN_KILL_ESRCH got define'd. When
defined, I see the problem; when I undefine BROKEN_KILL_ESRCH (the default),
the shell works fine. I'm wondering how this could end up being define'd...

On Tue, Jun 05, 2001 at 06:11:04AM +0000, Bart Schaefer wrote:
> } 29084:      Received signal #2, SIGINT, in sigsuspend() [caught]
> } 29084:  sigsuspend(0xFFBEF000)                          Err#4 EINTR
> 
> It would have been nice to see what came after that, but my guess is
> that `errflag' became true and we exited the loop that way.  The real
> question still is, why didn't we see the ESRCH error from kill(pid, 0)?

29084:  sigprocmask(SIG_BLOCK, 0x000DABE0, 0x000DABFC)  = 0
29084:  sigprocmask(SIG_SETMASK, 0xFFBEEBD8, 0xFFBEEB48) = 0
29084:  setcontext(0xFFBEECE8)
29084:  sigprocmask(SIG_BLOCK, 0x000DABE0, 0x000DABFC)  = 0
29084:  sigprocmask(SIG_UNBLOCK, 0x000DABE0, 0x000DABFC) = 0
29084:  llseek(11, 0, SEEK_CUR)                         = 13
29084:  close(11)                                       = 0
29084:  sigprocmask(SIG_BLOCK, 0x000DABE0, 0x000DABFC)  = 0
29084:  sigprocmask(SIG_UNBLOCK, 0x000DABE0, 0x000DABFC) = 0
29084:  ioctl(10, TIOCGSID, 0xFFBEF964)                 = 0
29084:  getsid(0)                                       = 9149
29084:  ioctl(10, TIOCSPGRP, 0xFFBEFA10)                = 0
29084:  fstat64(0, 0xFFBEF988)                          = 0
29084:  fcntl(0, F_GETFL, 0x00000000)                   = 2
29084:  fstat64(0, 0xFFBEF820)                          = 0
29084:  time()                                          = 991690436
29084:  time()                                          = 991690436
29084:  sigaction(SIGINT, 0xFFBEF988, 0x00000000)       = 0
29084:  sigaction(SIGINT, 0xFFBEF5E0, 0x00000000)       = 0
29084:  getuid()                                        = 3387 [3387]
29084:  ioctl(10, FIONREAD, 0xFFBEF644)                 = 0
29084:  ioctl(10, TIOCGSID, 0xFFBEF50C)                 = 0
29084:  getsid(0)                                       = 9149
29084:  ioctl(10, TIOCSPGRP, 0xFFBEF5B8)                = 0
29084:  ioctl(10, TCSETSW, 0xFFBEF648)                  = 0
29084:  write(10, "\r1B [ m1B [ m1B [ m1B [".., 20)     = 20
29084:  write(10, "1B [ K", 3)                          = 3
29084:  read(10, 0xFFBEF4CB, 1)         (sleeping...)
29084:  read(10, "04", 1)                               = 1
29084:  write(10, "\r\n", 2)                            = 2
29084:  alarm(0)                                        = 0
29084:  ioctl(10, TCSETSW, 0x000DAB04)                  = 0
29084:  getpid()                                        = 29084 [29083]
29084:  llseek(0, 0, SEEK_CUR)                          = 6483602
29084:  _exit(1)

Thanks,
-- 
Jos Backus                 _/  _/_/_/        "Modularity is not a hack."
                          _/  _/   _/                -- D. J. Bernstein
                         _/  _/_/_/             
                    _/  _/  _/    _/
josb@cncdsl.com     _/_/   _/_/_/            use Std::Disclaimer;


  parent reply	other threads:[~2001-06-05 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-04 21:37 Jos Backus
2001-06-05 10:12 ` Peter Stephenson
     [not found] ` <1010605061126.ZM4201@candle.brasslantern.com>
2001-06-05 21:16   ` Jos Backus [this message]
2001-06-08  4:50     ` Bart Schaefer
2001-06-08  6:15       ` Jos Backus

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=20010605141619.A36532@lizzy.bugworks.com \
    --to=josb@cncdsl.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).