[slime-devel] local variables lost in cmucl
Giorgos Pontikakis
gnp at freemail.gr
Sun Dec 4 11:28:22 UTC 2005
Hi,
I'm using CMUCL 19c and Slime from CVS. I get this strange
behaviour when I debug a lisp program:
-- When I compile and load my files with the following:
(dolist (i *source-files*)
(declaim (optimize (speed 0) (space 0) (safety 3) (debug 3)))
(compile-file (concatenate 'string i ".lisp")))
(dolist (i *source-files*)
(declaim (optimize (speed 0) (space 0) (safety 3) (debug 3)))
(load (concatenate 'string i ".x86f")))
I can use the 'v' command of the slime-debugger to see my source
code, but I lose information for local variables
-- When I just load the files using the following:
(dolist (i *source-files*)
(declaim (optimize (speed 0) (space 0) (safety 3) (debug 3)))
(load (concatenate 'string i ".lisp")))
I have information for local variables, but the 'v' command
of the debugger does not jump to the source code. Instead, it
presents me with some representation of the code which I believe
that is the interpreted one, and is much more difficult to use.
Is there something that I'm doing wrong, or is it a limitation
of slime?
thank you very much
Giorgos
More information about the slime-devel
mailing list