[slime-devel] leopard + sbcl + sb-thread

[Nikodemus Siivola]

On Sat, May 17, 2008 at 1:27 PM, Aaron Feng <aaron.feng at gmail.com> wrote:
> Hi Nikodemus,
>
> You are every where :)  Thanks for the tip.  Here is the backtrace:
>
> Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
> 0: (BACKTRACE 536870911 #<SYNONYM-STREAM :SYMBOL SB-SYS:*TTY* {13D03969}>)
> 1: ((LAMBDA NIL))
> 2: ((LAMBDA NIL))
> 3: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE # {13D03A85}>)
> 4: (SB-IMPL::ERROR-ERROR)
> 5: (SB-IMPL::INFINITE-ERROR-PROTECTOR)
> 6: (SB-KERNEL:INTERNAL-ERROR #.(SB-SYS:INT-SAP #X000F9000) #<unavailable
> argument>)
> 7: ("foreign function: call_into_lisp")
> 8: ("foreign function: funcall2")
> 9: ("foreign function: interrupt_internal_error")
> 10: ("foreign function: signal_emulation_wrapper")
> 11: ("foreign function: os_get_runtime_executable_path")
> 12: ("foreign function: os_get_runtime_executable_path")
> 13: (FIND-SYMBOL 68089408 #<PACKAGE "COMMON-LISP-USER">)

Is that all of it? Having a few frames below the FIND-SYMBOL would
help a lot, since that is where the interesting stuff would be...

Now your task is to figure out where the 68089408 is coming from, and
why FIND-SYMBOL is being called on it... If your Slime really a clean
CVS checkout? Do you have something strange in .sbclrc, etc?

Cheers,

 -- Nikodemus