[Bese-devel] Re: Getting ucw_box to work

[Lou Vanek]

Pupeno wrote:

> Another try.
> Just running sbcl, without slime, and loading start.lisp produces a more
> meaningful error:
> 
> pupeno at ulab:~/Software/hosting-compass/ucw-boxset$ sbcl
> This is SBCL 0.9.13, an implementation of ANSI Common Lisp.
> More information about SBCL is available at <http://www.sbcl.org/>.
> 
> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses.  See the CREDITS and COPYING files in the
> distribution for more information.
> * (load "start.lisp")
> STYLE-WARNING: implicitly creating new generic function
> EFFECTIVE-KEYWORD-NAME
> STYLE-WARNING: implicitly creating new generic function APPLY-LAMBDA/CC
> STYLE-WARNING: implicitly creating new generic function ENABLED-P
> STYLE-WARNING: implicitly creating new generic function LOG.LEVEL
> STYLE-WARNING: implicitly creating new generic function (SETF LOG.LEVEL)
> STYLE-WARNING: implicitly creating new generic function ENQUEUE
> STYLE-WARNING: implicitly creating new generic function DEQUEUE
> STYLE-WARNING: implicitly creating new generic function PEEK-QUEUE
> STYLE-WARNING: implicitly creating new generic function QUEUE-EMPTY-P
> STYLE-WARNING: implicitly creating new generic function QUEUE-FULL-P
> STYLE-WARNING: implicitly creating new generic function QUEUE-COUNT
> STYLE-WARNING:
>    implicitly creating new generic function
> CALL-FOR-ALL-ELEMENTS-WITH-INDEX
> STYLE-WARNING: implicitly creating new generic function GROW-QUEUE
> STYLE-WARNING: implicitly creating new generic function MOVE-TAIL
> STYLE-WARNING: implicitly creating new generic function MOVE-HEAD
> STYLE-WARNING: implicitly creating new generic function QUEUE->LIST
> STYLE-WARNING: implicitly creating new generic function
> ENQUEUE-OR-MOVE-TO-FRONT
> 
> debugger invoked on a SIMPLE-TYPE-ERROR in thread
> #<THREAD "initial thread" {A8235A9}>:
>   Argument X is not a REAL: NIL
> 
> Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
> 
> restarts (invokable by number or by possibly-abbreviated name):
>   0: [RETRY ] Retry performing #<ASDF:LOAD-OP NIL {A950AD1}> on
>               #<ASDF:CL-SOURCE-FILE "swank-loader" {A950AE1}>.
>   1: [ACCEPT] Continue, treating #<ASDF:LOAD-OP NIL {A950AD1}> on
>               #<ASDF:CL-SOURCE-FILE "swank-loader" {A950AE1}> as having
> been
>               successful.
>   2: [ABORT ] Exit debugger, returning to top level.
> 
> (SB-KERNEL:TWO-ARG-> NIL 3359602209)
> 0]

I'm assuming you're running on a 2.6+ Linux (sbcl says it supports threads
on this version of Linux).
What does the backtrace tell you about the error?
Doesn't sbcl have a verbose option that can tell you which function it was
compiling when it died?