The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] 211bsd kermit working
Date: Mon, 10 Aug 2020 09:12:32 -0400 (EDT)	[thread overview]
Message-ID: <20200810131232.14B6E18C082@mercury.lcs.mit.edu> (raw)

    > From: Will Senn

    > $c
    > 0177520: ~signal(016,01) from ~sysinit+034
    > 0177542: ~sysinit() from ~main+010
    > 0177560: _main() from start+0104

    > If this means it got signal 16... or 1 from the sysinit call (called
    > from main)

I'm not sure that interpretation is correct. I think that trace shows signal()
being called from sysinit().

On V6, signal() was a system call which one could use to set the handlers for
signals (or set them to be ignored, or back to the default action). In. 2.11
it seems to be a shim layer which provides the same interface, but uses
the Berserkly signal system interface underneath:

  https://www.tuhs.org/cgi-bin/utree.pl?file=2.11BSD/include/signal.h
  https://www.tuhs.org/cgi-bin/utree.pl?file=2.11BSD/man/cat3/signal.0

So maybe the old binary for kermit is still trying to use the (perhaps
now-removed) signal system call?

	     Noel


             reply	other threads:[~2020-08-10 13:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 13:12 Noel Chiappa [this message]
2020-08-10 13:24 ` Will Senn
  -- strict thread matches above, loose matches on Subject: below --
2020-08-09 21:05 Will Senn
2020-08-09 21:12 ` Clem Cole
2020-08-09 21:31   ` Will Senn
2020-08-10  0:53     ` Dave Horsfall
2020-08-10  1:42       ` Will Senn
2020-08-09 23:21 ` Warner Losh

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=20200810131232.14B6E18C082@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@minnie.tuhs.org \
    /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.
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).