From: Will Senn <will.senn@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 211bsd kermit working
Date: Sun, 9 Aug 2020 16:31:36 -0500 [thread overview]
Message-ID: <53608f1c-4bcc-a15c-7ca2-3317879a157c@gmail.com> (raw)
In-Reply-To: <CAC20D2N7yMsct+LT5rfR0mroSCj6YMFSzo5Lu4joFzhC2kdWVQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]
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. 's all greek to me at this point. I'm
super new to adb. I tried your approach adb /usr/new/kermit and it
brought up the adb prompt, so I gather it works that way too, but I
couldn't figure out how to run it from there. A quick perusal of the adb
man page didn't really help. I'm off to finish reading the ADB tutorial
that I bailed on last week in v7 after I hit the there's no fcreat in v7
issue :).
Will
On 8/9/20 4:12 PM, Clem Cole wrote:
> try this: adb /usr/new/kermit
> Then run it and let it crash. You'll get an adb prompt, look at the
> stack and see what system call number was pushed.
>
> I suspect it a versioning issue that Warner has been discussing as 2.X
> changed over time.
>
> That said, it might just be easier to try to recompile c-kermit.
>
> Clem
>
> On Sun, Aug 9, 2020 at 5:06 PM Will Senn <will.senn@gmail.com
> <mailto:will.senn@gmail.com>> wrote:
>
> I'm running 211bsd pl 431 in SimH on FreeBSD. I've got networking
> working on a tap interface both inbound and outbound. I still have
> a few issues hanging around that are bugging me, but I'll
> eventually get to them. One that is of concern at the moment is
> kermit. It is in the system under /usr/new/kermit. When I call it,
> I get:
>
> kermit
> Bad system call - core dumped
>
> I don't see core anywhere and if I did, I'd need to figure out
> what to do with it anyway (mabye adb), but I'm wondering if
> anyone's used kermit successfully who is on pl 431 or knows what's
> going on?
>
> Thanks,
>
> Will
>
> --
> GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
>
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
[-- Attachment #2: Type: text/html, Size: 4442 bytes --]
next prev parent reply other threads:[~2020-08-09 21:32 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 [this message]
2020-08-10 0:53 ` Dave Horsfall
2020-08-10 1:42 ` Will Senn
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=53608f1c-4bcc-a15c-7ca2-3317879a157c@gmail.com \
--to=will.senn@gmail.com \
--cc=clemc@ccc.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).