Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!think!rlk
From: rlk@think.COM (Robert Krawitz)
Newsgroups: comp.emacs
Subject: Re: using the internal Lisp debugger
Message-ID: <11946@think.UUCP>
Date: Wed, 18-Nov-87 13:51:26 EST
Article-I.D.: think.11946
Posted: Wed Nov 18 13:51:26 1987
Date-Received: Sat, 21-Nov-87 10:12:47 EST
Sender: usenet@think.UUCP
Reply-To: rlk@THINK.COM
Organization: Thinking Machines Corporation, Cambridge, MA
Lines: 22

In article <1759@culdev1.UUCP> drw@culdev1.UUCP (Dale Worley) writes:
]
]You can't debug anything if it is compiled into byte code.  You can
]get around this if you find-file the source file for the function you
]are interested in, and re-execute the defun that defines the function
](use eval-defun).

This isn't true.  You can debug byte-compiled functions, it's just
that they won't be quite so legible (the lexical structure of the
program might not be perfectly preserved).  The one thing you can't do
is debug subr's (Lisp functions hardcoded in C).

The V17 debugger sometimes had problems if you typed 'd' when there
were no more calls to make; in that case, it tried to debug the calls
to debug, leading to considerable confusion.  The V18 debugger lets
you debug by continuously typing 'd'.

cca >>>>>>>>>>  |
harvard >>>>>>  |
bloom-beacon >  |think!rlk	Robert Krawitz <rlk@think.com>
rutgers >>>>>>  |
ihnp4 >>>>>>>>  .