From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: Re: [TUHS] SDB debugger
Date: Sat, 2 May 2020 22:21:04 -0400 (EDT) [thread overview]
Message-ID: <20200503022104.181B54422F@lignose.oclsc.org> (raw)
Doug's list is slightly off:
adb v7-v10
sdb v8-v10
sdb may actually have been in V7; I'm quite sure
it was present in 32/V. But it's not in the V7
manual.
adb and sdb were certainly working fine when I
arrived in 1127, but they still used ptrace
because nobody wanted to touch the code. I used
adb quite often (still would were it available
in modern worlds!), so I cared enough to take
it over, restructuring it quite a bit to make it
easier to retarget for different instruction
sets and byte orders, and of course to use /proc.
I also made some trivial, compatible changes to
how numbers were read and printed to conform to
Rob's Rule (of which I am also a fan) that what
a program presents as output it should also
accept as input.
sdb I wasn't as fond of, but I did want to get
rid of ptrace, so I tinkered it just enough to
accomplish that.
I do remember clearly celebrating the death of
ptrace by removing ptrace(2) from the copy of the
V8 manual in the UNIX Room. It took up two
pages, and they happened to be facing pages,
so I glued them together.
I wish it was as easy for others to have such
satisfaction these days.
Norman Wilson
Toronto ON
next reply other threads:[~2020-05-03 2:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 2:21 Norman Wilson [this message]
2020-05-03 2:41 ` Larry McVoy
2020-05-03 7:14 ` arnold
2020-05-03 3:05 ` Rob Pike
-- strict thread matches above, loose matches on Subject: below --
2020-05-02 2:52 Doug McIlroy
2020-05-02 17:45 ` Larry McVoy
2020-05-03 16:16 ` Rich Morin
2020-05-12 4:36 ` Dave Horsfall
2020-05-01 20:48 Paul Ruizendaal
2020-05-01 21:57 ` Clem Cole
2020-05-02 9:10 ` Paul Ruizendaal
2020-05-02 16:04 ` Clem Cole
2020-05-01 23:05 ` Jeremy C. Reed
2020-05-02 0:49 ` Noel Hunt
2020-05-02 1:22 ` Rob Pike
2020-05-02 3:49 ` Noel Hunt
2020-05-02 20:16 ` Paul Ruizendaal
2020-05-03 6:58 ` arnold
2020-05-03 16:13 ` Clem Cole
2020-05-03 16:53 ` Henry Bent
2020-05-03 17:06 ` Henry Bent
2020-05-03 17:13 ` Henry Bent
2020-05-03 20:26 ` Clem Cole
2020-05-03 17:35 ` Paul Winalski
2020-05-03 21:27 ` Paul Ruizendaal
2020-05-12 4:15 ` Dave Horsfall
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=20200503022104.181B54422F@lignose.oclsc.org \
--to=norman@oclsc.org \
--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).