From: "Jeremy C. Reed" <reed@reedmedia.net>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] SDB debugger
Date: Fri, 1 May 2020 18:05:24 -0500 (CDT) [thread overview]
Message-ID: <alpine.NEB.2.21.2005011757220.4106@t1.m.reedmedia.net> (raw)
In-Reply-To: <2F4C604D-F01C-4A82-948A-7E77093B48A1@planet.nl>
> unknown. It also says that the original author of ?sdb? is unknown. Is
> that correct, is the author really unknown?
Howard Katseff
See 3BSD: usr/doc/sdb/sdbrp.n
and
https://www.usenix.org/legacy/publications/library/proceedings/cinci93/full_papers/katseff.txt
I had also done some interview with him. My Book (wip) says:
Katseff, who had already graduated from Berkeley in August 1978,
was working at Bell Labs in Holmdel
in the group developing 32/V. He started working on
sdb, a symbolic debugger for C language programs. It was used
for debugging core images from aborted programs. It could report
which original source code line caused the error, allowed
access to variables, define breakpoints, calling procedures,
and could single step on a line by line basis.
(Haley and Joy had provided constructive criticism during the sdb
development.)
% cite: archives/1970s/3bsd/usr/doc/sdb/sdbrp.n
% NOTE: Katseff didn't remember if that is for doc or code
This debugger was transferred to Berkeley along with the rest of
the 32/V operating system.\cite{katseff1}
next prev parent reply other threads:[~2020-05-01 23:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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-05 0:22 ` [TUHS] DEC Compilers (was: " Win Treese
2020-05-05 17:36 ` Paul Winalski
2020-05-05 18:53 ` Dr Iain Maoileoin
2020-05-05 21:59 ` Dan Cross
2020-05-05 21:49 ` Henry Bent
2020-05-03 17:35 ` [TUHS] " Paul Winalski
2020-05-03 21:27 ` Paul Ruizendaal
2020-05-12 4:15 ` Dave Horsfall
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-03 2:21 Norman Wilson
2020-05-03 2:41 ` Larry McVoy
2020-05-03 7:14 ` arnold
2020-05-03 3:05 ` Rob Pike
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=alpine.NEB.2.21.2005011757220.4106@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
--cc=pnr@planet.nl \
--cc=tuhs@minnie.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).