The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] SDB debugger
Date: Sun, 3 May 2020 12:13:09 -0400	[thread overview]
Message-ID: <CAC20D2P6L1DPdDW4rhBXD-9v9AhZ2Of339GFLsUVmmiQ+LMu7Q@mail.gmail.com> (raw)
In-Reply-To: <21F16C75-62AB-422A-A43F-981407E11434@planet.nl>

[-- Attachment #1: Type: text/plain, Size: 2324 bytes --]

On Sat, May 2, 2020 at 4:16 PM Paul Ruizendaal <pnr@planet.nl> wrote:

> The dbx debugger appears to stand on the shoulders of sdb, and gdb on the
> shoulders of dbx.
>
Mumble ...   It's true rms started with dbx and peed on it in their
usually way - similar to the Gosling EMACS to GnuEMACS story.

But  Mark wrote DBX from scratch, although I would be surprised if looked
at how adb and sdb handled the symbol table and could have lifted that code
from their.   If I remember discussions with him about it, his interface
model was really more VMS debugger more than sdb.   As I said, I really
don't remember anyone at UCB in those days using sdb.

At the time, there was a huge push (mostly from the Stanford crew) to make
VMS the Arpa standard system replacing the PDP-10, TOPS, Tenex, ITS, et
al.  Besides the performance argument (hence the 4.1 FASTVAX work), one of
the arguments from the pro-VMS side was the language toolchain, including
comments that UNIX did not have a debugger in the same vein as VMS (and
also that the Fortran system was considered pretty weak).

When he was still at UCB, Mark had tried to make sure dbx worked with both
C and Fortran (i.e. at the beginning of the project I did some testing for
him because I was working on a large array processor in the CAD group, that
needed to compile EE CAD suite which at that point was heavily dominated by
Fortran codes).  The whole BSD UNIX Fortran was not great and I know when
Masscomp built their debugger, they started with dbx and had to gut the
multiple language support (thus rewriting much of the Fortran & Pascal
support); but the person that did it, had been part of DEC's TLG team
previously and had a direct knowledge of how the DEC debugger actually
handled multiple languages.    BTW the time, I personally did not really
care, as long as C support worked.

Paul W -- do you remember if DEC TLG did a version of dbx for Ultrix
(Leslie might remember)?  FWIW: I know that DEC had a number of different
debugger projects so on the UNIX side over the years, and I really don't
remember what was done for the VAX, as I was not there at the time.  By
MIPS/Alpha in the mid-late 90's there was a whole new debugger stream that
had been developed at part of GEM, but there was another one that came from
MIPs too which was based on dbx.

Clem

[-- Attachment #2: Type: text/html, Size: 3751 bytes --]

  parent reply	other threads:[~2020-05-03 16:14 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
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 [this message]
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=CAC20D2P6L1DPdDW4rhBXD-9v9AhZ2Of339GFLsUVmmiQ+LMu7Q@mail.gmail.com \
    --to=clemc@ccc.com \
    --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).