From: Henry Bent <henry.r.bent@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] SDB debugger
Date: Sun, 3 May 2020 13:06:54 -0400 [thread overview]
Message-ID: <CAEdTPBdRjWSJ-oJqyEyWBqoT+syLK==iZ51wxN49=LAAAEOXng@mail.gmail.com> (raw)
In-Reply-To: <CAEdTPBdFDPySSS8LxVhtSqi3PH+wuiaUo0tQ=HxZni2BDdEKwg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
On Sun, 3 May 2020 at 12:53, Henry Bent <henry.r.bent@gmail.com> wrote:
> On Sun, 3 May 2020 at 12:14, Clem Cole <clemc@ccc.com> wrote:
>
>>
>> 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.
>>
>
> Perhaps unsurprisingly, as Ultrix 1 was basically just 4.2BSD with some
> tweaks/addons, dbx has been there since the beginning as /usr/ucb/dbx. The
> binary in 1.1 has SCCS strings mostly dating it to '83 and the 2.0 source
> tree has dates that are mostly December '84.
>
Ultrix-32m 1.0 also has dbx, with dates no later than August '83. These
dates mostly correspond to the 4.2 source tree on TUHS (
https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/ucb/dbx ) but
not exactly - the 4.2 tree has a newer object.c, implying that DEC was
getting early copies of 4.2. The later fixes in Ultrix 1.1 also imply that
DEC was getting regular updates from UCB.
-Henry
[-- Attachment #2: Type: text/html, Size: 2138 bytes --]
next prev parent reply other threads:[~2020-05-03 17:07 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
2020-05-03 16:53 ` Henry Bent
2020-05-03 17:06 ` Henry Bent [this message]
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='CAEdTPBdRjWSJ-oJqyEyWBqoT+syLK==iZ51wxN49=LAAAEOXng@mail.gmail.com' \
--to=henry.r.bent@gmail.com \
--cc=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).