9 Aug
2020
9 Aug
'20
9:05 p.m.
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
9 Aug
9 Aug
9:12 p.m.
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(a)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
9:31 p.m.
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(a)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
10 Aug
10 Aug
12:53 a.m.
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
1:42 a.m.
On 8/9/20 7:53 PM, Dave Horsfall wrote:
On Sun, 9 Aug 2020, Will Senn wrote:
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
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 
9 Aug
9 Aug
11:21 p.m.
Maybe rebuild kermit? A crapton of compat stuff was removed over time.
Maybe the binary is stale?
Warner
On Sun, Aug 9, 2020, 3:06 PM Will Senn <will.senn(a)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
1349
days inactive
1350
days old
5 comments
4 participants
participants (4)
-
Clem Cole -
Dave Horsfall -
Warner Losh -
Will Senn