Page 1 of 1

Emacs + Clisp + Slime = messy backtrace

PostPosted: Mon Sep 22, 2008 8:59 am
by humpolec
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]

;; ...

Backtrace:
  0: [362] frame binding variables (~ = dynamically):
       | ~ SWANK::*SLDB-STEPPING-P* <--> NIL
  1: [359] frame binding variables (~ = dynamically):
       | ~ SWANK::*SLDB-LEVEL* <--> 0
  2: [356] frame binding variables (~ = dynamically):
       | ~ *PACKAGE* <--> #<PACKAGE COMMON-LISP-USER>
 
;;  ... lots of swank and sldb frames ...

 20: [285] EVAL frame for form FORTY-TWO
 21: [280] EVAL frame for form (+ 2 FORTY-TWO)
 22: [277] 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?

Re: Emacs + Clisp + Slime = messy backtrace

PostPosted: Fri Sep 26, 2008 4:37 pm
by AlexPaes
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.