From: Will Senn <will.senn@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, tuhs@minnie.tuhs.org
Subject: Re: [TUHS] 211bsd kermit working
Date: Mon, 10 Aug 2020 08:24:17 -0500 [thread overview]
Message-ID: <2cd016ff-3441-2c0e-ec22-85cba2b67293@gmail.com> (raw)
In-Reply-To: <20200810131232.14B6E18C082@mercury.lcs.mit.edu>
On 8/10/20 8:12 AM, Noel Chiappa wrote:
> > 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
>
Noel,
That makes a lot more sense. I'm still trying to locate source.
Thanks,
Will
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
next prev parent reply other threads:[~2020-08-10 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 13:12 Noel Chiappa
2020-08-10 13:24 ` Will Senn [this message]
-- 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=2cd016ff-3441-2c0e-ec22-85cba2b67293@gmail.com \
--to=will.senn@gmail.com \
--cc=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).