From: Larry McVoy <lm@mcvoy.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] SDB debugger
Date: Sat, 2 May 2020 10:45:18 -0700 [thread overview]
Message-ID: <20200502174518.GC30768@mcvoy.com> (raw)
In-Reply-To: <202005020252.0422qnFL066007@tahoe.cs.Dartmouth.EDU>
So I definitely remember adb, I liked it for the same reasons that Rob
did, it told you the truth.
I also remember using a sdb debugger, not sure if it was at Sun or
when I was doing a Sys V port. I liked it, it was reasonable.
I think dbx ended up becoming the one I used on BSD. Gdb eventually
got good enough but I'm with Rob, it was a mess early on.
But truth be known, I'm sort of a printf() debugger. The main thing
I use gdb for is a stack trace, that's usually enough. The BitKeeper
source has this "gem":
void
gdb_backtrace(void)
{
FILE *f;
char *cmd;
unless (getenv("_BK_BACKTRACE")) return;
unless ((f = efopen("BK_TTYPRINTF")) ||
(f = fopen(DEV_TTY, "w"))) {
f = stderr;
}
cmd = aprintf("gdb -batch -ex backtrace '%s/bk' %u 1>&%d 2>&%d",
bin, getpid(), fileno(f), fileno(f));
system(cmd);
free(cmd);
if (f != stderr) fclose(f);
}
On Fri, May 01, 2020 at 10:52:49PM -0400, Doug McIlroy wrote:
> > Does anyone know if dbx ended up 8 or 9th
>
> I believe the only debuggers on research machines were
> db v1-v6
> adb v7,v9,v10
> cdb v3-v6
> sdb v8-v9
> pi v8-v10
>
> Doug
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2020-05-02 17:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 2:52 Doug McIlroy
2020-05-02 17:45 ` Larry McVoy [this message]
2020-05-03 16:16 ` Rich Morin
2020-05-12 4:36 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
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
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=20200502174518.GC30768@mcvoy.com \
--to=lm@mcvoy.com \
--cc=doug@cs.dartmouth.edu \
--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).