home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.arch:8909 comp.lang.c:12354 comp.programming:2329 comp.unix.programmer:4312
- Path: sparky!uunet!mcsun!uknet!mucs!m1!bevan
- From: bevan@cs.man.ac.uk (Stephen J Bevan)
- Newsgroups: comp.arch,comp.lang.c,comp.programming,comp.unix.programmer
- Subject: Re: Summary of responses [was: What would you like from a debugger?]
- Message-ID: <BEVAN.92Aug14130951@jaguar.cs.man.ac.uk>
- Date: 14 Aug 92 12:09:51 GMT
- References: <bosullvn.713613694@unix1.tcd.ie> <id.SKBS.RIL@ferranti.com>
- Sender: news@cs.man.ac.uk
- Followup-To: comp.arch
- Organization: Department of Computer Science, University of Manchester
- Lines: 17
- In-reply-to: peter@ferranti.com's message of 13 Aug 92 15:24:31 GMT
-
- In article <id.SKBS.RIL@ferranti.com> peter@ferranti.com (Peter da Silva) writes:
- In article <bosullvn.713613694@unix1.tcd.ie> bosullvn@unix1.tcd.ie (Bryan O'Sullivan) writes:
- > I haven't decided yet what constitutes the smallest
- > debugger I can get away with, but such things as printing data
- > structures and their contents on the fly are out of the question.
-
- Embed an interpreted language in the debugger (drive it from TCL?).
-
- You mean like Norman Ramsey's use of PostScript as the "little
- language" with which to drive his debugger "ldb"?
- Check out PLDI '92 pp 22-31
-
- Note it also mentions TCL and FORTH as possible language, but notes
- that: "The latter [TCL and FORTH] two offer too few datatypes"
- Make of that what you will.
-
- bevan
-