[Bese-devel] Re: Help installing UCW

[Marco Baringer]

Erick Ivaan Lopez Carreon wrote:

> 109: (SB-IMPL::PROCESS-EVAL-OPTIONS ("(defmethod print-object ((c
> asdf::missing-component) s)
>                             (format s \"Unable to find the system for
> ~S.
> asdf:*central-registry* is ~S.
> Are the symlinks and asdf:*central-registry* properly setup?\"
> (asdf::missing-requires c)
> asdf:*central-registry*))" "(mapc (lambda (name) (asdf:oos 'asdf:load-op
> name)) '(:ucw :ucw.mod-lisp :ucw.admin :ucw.examples))"
> "(ucw:start-swank)" "(ucw:create-server :backend :mod-lisp
>                                              :host \"127.0.0.1\"
>                                              :port 3000
>                                              :applications (list
> it.bese.ucw-user::*example-application*
>                     ucw::*admin-application*)
>                                              :debug-on-error T
>                                              :inspect-components NIL
>                                              :log-root-directory #P
> \"/home/user/.sbcl/site//logs/\"
>                                              :log-level it.bese.arnesi:
> +INFO+)"))
> 110: (SB-IMPL::TOPLEVEL-INIT)
> 111: ((LABELS SB-IMPL::RESTART-LISP))
> 
> debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial
> thread" {A90E321}>: Maximum error nesting depth exceeded

this means that someone, somewhere, is lost in an infinite recursion loop :(

> 
> 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 {B903201}> on
> #<ASDF:CL-SOURCE-FILE "package" {B78D829}>.

the only package, of the ones you listed above, that has a file named
package.lisp is parenscript (afaik). what happens if you do a simple
(asdf:oos 'asdf:load-op :parenscript) ?

>   1: [ACCEPT  ] Continue, treating #<ASDF:LOAD-OP NIL {B903201}> on
> #<ASDF:CL-SOURCE-FILE "package" {B78D829}> 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).
> 
> ((LAMBDA (SB-IMPL::E)) #<SB-FASL::INVALID-FASL-VERSION {B3F91C1}>)

this is definetly odd, you should be getting a 'stale fasl' error
message if this is the case.

> Any clues??

mrs. plum, in the kitchen, with the rope :)

did you upgrade sbcl recently? the first thing to do is try and delete
all the .fasl files you have lying around (including slime's .slime
directory) and reload. should that fail try loading the system one by
one, in order, and see who breaks, send me a complete backtrace
(including stack locals) and i'll see who's fault it is.

-- 
-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