From: Rob Pike <email@example.com>
To: Norman Wilson <firstname.lastname@example.org>
Cc: The Eunuchs Hysterical Society <email@example.com>
Subject: Re: [TUHS] v7 source code for sh
Date: Tue, 22 Feb 2022 05:10:14 +1100 [thread overview]
Message-ID: <CAKzdPgzPdfxUxLHpmkuRVFZunp3N_weikk1uPgB8_P2VEn8EFg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
It was likely me, as I did a lot of work on the program, but I don't claim
that I was the one.
There is a db (the Plan 9 derivation of adb) in plan9port, but it struggles
with modern binaries.
On Tue, Feb 22, 2022 at 5:00 AM Norman Wilson <firstname.lastname@example.org> wrote:
> Rob Pike:
> I did the same to adb, which turned out to have a really good debugger
> hidden under a few serious bugs of its own, which I fixed.
> Was it you who replaced ptrace with /proc in adb, or did I do that?
> I do remember I was the one who took ptrace out of sdb (which a
> few 1127-ers, or perhaps 112-ers on alice and rabbit still used).
> After which I removed ptrace from the kernel, and from the
> copy of the V8 manual in the UNIX room. Conveniently ptrace
> occupied two facing pages; I glued them together.
> I also later did some work to try to isolate the target-dependent
> parts of adb and to make them work in host-independent ways--e.g.
> assembling ints byte-by-byte rather than assuming byte order--to
> make it easier to make a cross adb, e.g. to examine PDP-11 or
> 68K core dumps on a VAX.
> I miss adb; maybe it's time to revive it, though these days I'd
> be tempted to rewrite it in Python so I could just load the right
> module at runtime to pick the desired target.
> Norman Wilson
> Toronto ON
[-- Attachment #2: Type: text/html, Size: 1794 bytes --]
next prev parent reply other threads:[~2022-02-21 18:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 17:58 Norman Wilson
2022-02-21 18:10 ` Rob Pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-22 3:07 Brian Walden
2022-02-22 14:28 ` Chet Ramey
2022-02-22 14:47 ` Clem Cole
2022-02-20 7:24 Rudi Blom
2022-02-19 17:44 Bakul Shah
2022-02-19 18:44 ` Rob Pike
2022-02-19 19:29 ` Clem Cole
2022-02-19 22:39 ` John Cowan
2022-02-19 23:11 ` Sven Mascheck
2022-02-19 23:34 ` Rob Pike
2022-02-19 23:36 ` silas poulson
2022-02-20 20:54 ` Chet Ramey
2022-02-20 21:02 ` Larry McVoy
2022-02-20 21:19 ` Chet Ramey
2022-02-20 21:19 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-02-20 22:39 ` Chet Ramey
2022-02-21 1:01 ` Dan Cross
2022-02-22 4:54 ` Dan Stromberg
2022-02-22 5:39 ` Rob Pike
2022-02-22 5:54 ` George Michaelson
2022-02-19 15:43 Will Senn
2022-02-19 16:03 ` Steve Nickolas
2022-02-19 16:07 ` Clem Cole
2022-02-19 16:43 ` Steve Nickolas
2022-02-19 17:24 ` Ron Natalie
2022-02-19 16:04 ` Clem Cole
2022-02-19 16:06 ` Bakul Shah
2022-02-19 16:57 ` Will Senn
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).