The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] v6 debugging
Date: Sat, 23 Jan 2016 12:39:45 -0500	[thread overview]
Message-ID: <CAC20D2Nfw5MajDE+1QBtDCGMzDbhQMtxiR_Vf31UYZiAgjgLxg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2N39YsNWsh05CacBt9KR6xGw5Ueb1nGP4wxzBtyHZHuAQ@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

On Sat, Jan 23, 2016 at 12:30 PM, Clem Cole <clemc at ccc.com> wrote:

> 3. No debugger that I can find.
>>
> ​From research, until V7 correct.  But check the USENIX tapes, ​Harvard,
> CU or Columbia did a ddt clone that was pretty good.
>

​Just read Noel's message -- sounds like the ddt came from Stanford and
MIT.   I don't remember the assembler version of it, but we definitely had
a C version for the 11 before V7.

I also had forgotten about db and cdb  - I could not tell you when they
appeared in the source stream without poking at Warren's archives.

BTW: I was thinking that the ddt came from the CU folks because they were
the folks that first got the DEC FTN to run on UNIX.  Since they did not
have access to  PDP-10 to run the BLISS compiler, the simulated it.   They
wrote a number of tools for the 11 and 10 in that project what were much
like the DEC tools from the PDP-10.


Clem​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160123/72734314/attachment-0001.html>


  reply	other threads:[~2016-01-23 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23 16:58 Will Senn
2016-01-23 17:25 ` Brantley Coile
2016-01-23 17:30 ` Clem Cole
2016-01-23 17:39   ` Clem Cole [this message]
2016-01-23 17:18 Noel Chiappa
2016-01-23 17:38 ` Will Senn
2016-01-23 18:03 Noel Chiappa
2016-01-23 18:42 ` Will Senn
2016-01-25 15:12 Noel Chiappa
2016-01-25 15:12 Noel Chiappa
2016-01-25 15:26 ` Clem Cole

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=CAC20D2Nfw5MajDE+1QBtDCGMzDbhQMtxiR_Vf31UYZiAgjgLxg@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).