From: Will Senn <will.senn@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] 211bsd kermit working
Date: Sun, 9 Aug 2020 20:42:53 -0500 [thread overview]
Message-ID: <ccf5f93b-7421-60bb-e76a-09fb40ec1bc4@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2008101050130.3620@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On 8/9/20 7:53 PM, Dave Horsfall wrote:
> On Sun, 9 Aug 2020, Will Senn wrote:
>
>> Well, that sure sounds easy. I found the core file and figured out that:
>>
>> adb /usr/new/kermit kermit.core
>>
>> was the incantation to load stuff into adb. $c is the stack trace:
>> $c
>> 0177520: ~signal(016,01) from ~sysinit+034
>> 0177542: ~sysinit() from ~main+010
>> 0177560: _main() from start+0104
>> adb> ^D
>>
>> If this means it got signal 16... or 1 from the sysinit call (called
>> from main), then according to man signal 16's urgent condition
>> present on socket, and 01's just hangup. [...]
>
> Is not "016" octal i.e. 14 i.e. SIGTERM in older versions of *x?
>
> -- Dave
Good catch on the octal, but here's the list from man signal:
SIGALRM 14 alarm clock
SIGTERM 15 software termination signal
SIGURG 16@ urgent condition present on socket
So, SIGALRM? Hmm.. I'm prolly gonna try to rebuild as Warner suggests...
if I can locate the src.
Will
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
[-- Attachment #2: Type: text/html, Size: 1919 bytes --]
next prev parent reply other threads:[~2020-08-10 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2020-08-09 23:21 ` Warner Losh
2020-08-10 13:12 Noel Chiappa
2020-08-10 13:24 ` Will Senn
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=ccf5f93b-7421-60bb-e76a-09fb40ec1bc4@gmail.com \
--to=will.senn@gmail.com \
--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).