From: Jacob Ritorto <jacob.ritorto@gmail.com>
To: Ronald Natalie <ron@ronnatalie.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] as(1) on Ultrix-11 vs 2.11BSD
Date: Wed, 29 Apr 2020 00:08:35 -0400 [thread overview]
Message-ID: <CAHYQbfDUD7Mup6ko7g4hMAio1Q2u1T_9hRmxCYwJtUMogENQzQ@mail.gmail.com> (raw)
In-Reply-To: <20200429022654.D43FA18C08D@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]
Shoot, celebrated too soon. I rearranged it per your tutelage, Ron, and
it's still giving an Illegal Instruction error!
From the adb output it looks like it's balking at the "14" instruction at
location 24, which, based on the BSD updates you mentioned, I thought
should've been taken as an arg, not an instruction, right?
I assume this worked for you on some BSD, right?
If so, is it a bug in the recent 2.11BSD patch release, perhaps? Anyone
able to help me understand?
> vi hello.s
"hello.s" 8 lines, 52 characters
sys 4
1
a
6
sys 1
0
a: <Hello\n>
"hello.s" 7 lines, 78 characters
> as !$
as hello.s
> ./a.out
Illegal instruction (core dumped)
> od a.out
0000000 000407 000022 000000 000000 000010 000000 000000 000000
0000020 104404 000001 000014 000006 104401 000000 062510 066154
0000040 005157 000000 000000 000002 000000 000000 000000 000000
0000060 000000 000000 000000 000004 000002 000014 000000 000006
0000100 000141
0000102
> adb
adb> :s
stopped at 0: sys write
adb> :s
a.out: running
stopped at 04: <illegal op> 014
adb> :s
a.out: running
Illegal instruction
stopped at 06: rtt
adb> :s
a.out: running
Illegal instruction - core dumped
process terminated
adb> >
On Tue, Apr 28, 2020 at 10:26 PM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
> > From: Jacob Ritorto
>
> > I wonder if the differences are written up somewhere. I did try to
> look
> > for more documentation but came up short.
>
> Sounds like a perfect topic for a CHWiki page. :-) E.g. this one:
>
> http://gunkies.org/wiki/Unix_V6_internals
>
> which I did as a bit of an addendum to Lions, to explain rsav, qsav and
> ssav, and
> similar topics.
>
>
> I noticed in the comparison of your two binary files that the instructions
> looked the same, but the a.out headers had a difference, but I didn't
> remember
> the fields in the a.out header enough to know what the differences meant.
>
> I thought I remembered doing an a.out page there, but apparently not. I
> thought about doing one now, but decided it wasn't worth it; I just needed
> to
> spin up my V6 system and do 'man a.out'! :-)
>
> Noel
>
>
[-- Attachment #2: Type: text/html, Size: 3074 bytes --]
next prev parent reply other threads:[~2020-04-29 4:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 2:26 Noel Chiappa
2020-04-29 4:08 ` Jacob Ritorto [this message]
2020-04-29 12:20 ` Ronald Natalie
-- strict thread matches above, loose matches on Subject: below --
2020-04-29 13:55 Paul Ruizendaal
2020-04-29 14:18 ` ron
2020-04-30 21:49 ` Alexander Voropay
2020-04-30 22:06 ` Clem Cole
2020-04-30 22:09 ` Clem Cole
2020-05-01 0:12 ` Ronald Natalie
2020-04-28 1:56 Jacob Ritorto
2020-04-28 13:03 ` Ronald Natalie
2020-04-29 0:17 ` Jacob Ritorto
2020-04-29 0:54 ` ron
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=CAHYQbfDUD7Mup6ko7g4hMAio1Q2u1T_9hRmxCYwJtUMogENQzQ@mail.gmail.com \
--to=jacob.ritorto@gmail.com \
--cc=ron@ronnatalie.com \
--cc=tuhs@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).