[Bese-devel] new start.lisp problems
Marco Baringer
mb at bese.it
Sat May 14 18:22:58 UTC 2005
Jason Wang <randomtalk at gmail.com> writes:
> hi, i have tried to start up ucw yesterday evening, after two days of
> pause.. However, it doesn't work anymore for some reason (i didn't
> touch it since last time running).. today morning, i upgraded
> everything to latest from tla.. and the problem persists.
>
> When i run ./bin/ucwctl start && ./bin/ucwctl attach, it loads
> start.lisp, and returns the following error:
> debugger invoked on a SIMPLE-ERROR in thread 4493:
> Error during processing of --eval option "(|LOAD|
> \"/var/www/ucw/bin/start.lisp\")":
>
> 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 {95959B9}> on
> #<ASDF:CL-SOURCE-FILE "swank-loader" {95802B9}>.
> 1: [ACCEPT ] Continue, treating #<ASDF:LOAD-OP NIL {95959B9}> on
> #<ASDF:CL-SOURCE-FILE "swank-loader" {95802B9}> as having been
> successful.
> 2: [CONTINUE] Ignore and continue with next --eval option.
> 3: [ABORT ] Skip rest of --eval options.
> 4: Skip to toplevel READ/EVAL/PRINT loop.
> 5: [QUIT ] Quit SBCL (calling #'QUIT, killing the process).
>
> anyone know what's wrong?
this has been happening to a LOT of people lately :(
this gist is that asdf is comparing the file-write-dates of two files,
one of which doesn't exist, and this is causing #'< (or maybe its
#'MAX) to return an error. since you get this error on swank-loader
i'd suggest killing your ~/.slime/fasl directory and seeing if the
problem pressits.
ucw is (afaik) the only external app which uses slime so maybe
something has changed in slime and i haven't upgraded ucw yet, if the
problme persists we'll look closer.
--
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
-Leonard Cohen
More information about the bese-devel
mailing list