Discussion of programming Lisps using Emacs, including SLIME and other tools
- Posts: 14
- Joined: Sun Aug 17, 2008 1:37 pm
- Location: Poland
Every time I enter the debugger in Slime, it looks like this:
Code: Select all
EVAL: variable FORTY-TWO has no value
[Condition of type SYSTEM::SIMPLE-UNBOUND-VARIABLE]
0:  frame binding variables (~ = dynamically):
| ~ SWANK::*SLDB-STEPPING-P* <--> NIL
1:  frame binding variables (~ = dynamically):
| ~ SWANK::*SLDB-LEVEL* <--> 0
2:  frame binding variables (~ = dynamically):
| ~ *PACKAGE* <--> #<PACKAGE COMMON-LISP-USER>
;; ... lots of swank and sldb frames ...
20:  EVAL frame for form FORTY-TWO
21:  EVAL frame for form (+ 2 FORTY-TWO)
22:  frame binding environments
VAR_ENV <--> NIL
FUN_ENV <--> NIL
BLOCK_ENV <--> NIL
GO_ENV <--> NIL
DECL_ENV <--> ((DECLARATION OPTIMIZE DECLARATION))
23: <1/272> #<SYSTEM-FUNCTION EVAL>
- (+ 2 FORTY-TWO)
;; .... more unrelated frames
So if I want to identify source of the error, I have to dig through many irrelevant backtrace frames, related to the debugger and frontend. Is there any way to hide them?
- Posts: 21
- Joined: Sat Jun 28, 2008 3:38 am
- Location: Lisbon, Portugal
I just started messing around with clisp on windows and i too am struggling with all those slime+clisp messy debug messages. It's quite frustrating, I was trying to get clg to run on clisp 2.45 and i get several errors that i can't easily solve because i can't easily find the source of the problem.
If anyone knows of any way to have better debugging in clisp+slime i'd also be very interested in hearing it. Thanks.
CL-USER> (setf *boss* (make-instance 'smart-person))