Emacs + Clisp + Slime = messy backtrace
Posted: Mon Sep 22, 2008 8:59 am
Every time I enter the debugger in Slime, it looks like this:
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?
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