The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Disassemblers
Date: Sat, 19 Jun 2021 16:14:34 -0700	[thread overview]
Message-ID: <20210619231434.GK13979@mcvoy.com> (raw)
In-Reply-To: <CAC20D2O5hXaC0kmDq12T2bmzAi4mg-X0_CkKpVva9W52xTFmgQ@mail.gmail.com>

Rob: "it was arcane but remarkably powerful"

Pretty much sums it up.  Wasn't your friend when you were a newbie, was
really your friend once you got to know it.

On Sat, Jun 19, 2021 at 06:55:07PM -0400, Clem Cole wrote:
> Ah -- if it was adb you redid, no doubt of its power.  I used adb for a
> long time -- PDP-11/VAX/68K but as you said, you could learn a lot about
> your system.   FWIW:  we embedded adb into RTU, calling it kdb.   We didn't
> have no fancy VMs to run the system under, when it halted, it halted.   On
> a personal machine that was not a problem and adb/kdb was very cool.
> 
> Clem
> 
> On Sat, Jun 19, 2021 at 5:50 PM Rob Pike <robpike@gmail.com> wrote:
> 
> > Although upon reflection, I think what I did was fix 'adb' and call it
> > 'db'. Haven't had my coffee yet this morning.
> >
> > -rob
> >
> >
> > On Sun, Jun 20, 2021 at 7:49 AM Rob Pike <robpike@gmail.com> wrote:
> >
> >> For v8 or thereabouts, I spent some time fixing some fundamental bugs in
> >> db and found that it was arcane but remarkably powerful. Since it was lower
> >> level, it avoided the endemic debugging problem of misleading you about
> >> your program: All it could do was tell you what the machine was doing.
> >> (Cdb, sdb, and adb were, at least in my experience, always lying to you.) I
> >> may be the only person who appreciated db fully. Once the bugs were gone
> >> you really could use it to good effect, as long as you understood the CPU.
> >>
> >> But it was buggy and arcane, no question about that.
> >>
> >> -rob
> >>
> >>
> >>
> >>
> >> On Sun, Jun 20, 2021 at 6:46 AM Richard Salz <rich.salz@gmail.com> wrote:
> >>
> >>> I remember compiling and playing Langston's "empire" that I was told
> >>> came from a decompiled executable. This was in the 4.2 days.
> >>>
> >>

-- 
---
Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 

  reply	other threads:[~2021-06-19 23:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 15:04 Henry Bent
2021-06-19 15:54 ` Clem Cole
2021-06-19 16:33   ` Henry Bent
2021-06-19 16:59     ` Clem Cole
2021-06-19 20:44       ` Richard Salz
2021-06-19 21:49         ` Rob Pike
2021-06-19 21:50           ` Rob Pike
2021-06-19 22:55             ` Clem Cole
2021-06-19 23:14               ` Larry McVoy [this message]
2021-06-20  1:41             ` Brantley Coile
2021-07-02  1:36       ` scj
2021-07-02 16:56         ` Paul Winalski
2021-07-02 17:45           ` Paul Winalski
2021-07-02 18:07           ` John P. Linderman
2021-06-19 17:57 Noel Chiappa
2021-06-19 18:40 ` Clem Cole
2021-06-20  1:15 Norman Wilson

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=20210619231434.GK13979@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=clemc@ccc.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).