From: Vamsee K. <vam...@gm...> - 2007-05-22 21:47:45
|
Hi, I was trying to deploy a webapp on a Xen-based vps, where I'm using the binary 1.0.5 release. Though loading the webapp on my development system works fine, trying do deploy it on the vps gives me several of these errors: debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial thread" {A695679}>: overwriting old FUN-INFO #<SB-C::FUN-INFO :ATTRIBUTES (FOLDABLE FLUSHABLE SB-C::UNSAFELY-FLUSHABLE)> for ROTATE-BYTE Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [CONTINUE] Go ahead, overwrite it. 1: [RETRY ] Retry performing #<ASDF:LOAD-OP NIL {AAF6589}> on #<ASDF:CL-SOURCE-FILE "compiler" {A994189}>. 2: [ACCEPT ] Continue, treating #<ASDF:LOAD-OP NIL {AAF6589}> on #<ASDF:CL-SOURCE-FILE "compiler" {A994189}> as having been successful. 3: [ABORT ] Exit debugger, returning to top level. (SB-C::%DEFKNOWN (ROTATE-BYTE) (SFUNCTION (INTEGER BYTE-SPECIFIER INTEGER) INTEGER) 112) 0] 0 I'm not sure what the cause of these errors might be. Can somebody throw some light on this? Thanks, Vamsee. |
From: Juho S. <js...@ik...> - 2007-05-23 21:56:47
|
Vamsee Kanakala <vam...@gm...> writes: > Hi, > > I was trying to deploy a webapp on a Xen-based vps, where I'm using the > binary 1.0.5 release. Though loading the webapp on my development system > works fine, trying do deploy it on the vps gives me several of these errors: > > debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial thread" > {A695679}>: > overwriting old FUN-INFO > #<SB-C::FUN-INFO :ATTRIBUTES (FOLDABLE FLUSHABLE > SB-C::UNSAFELY-FLUSHABLE)> > for ROTATE-BYTE You're trying to load the sb-rotate-byte contrib (which is a dependency of sb-md5) multiple times into the same image. That should not be happening. The only ways I can imagine that happening would be due to using the :force t argument for asdf:load-op, or some really baroque scenarios involving transferring core files with sb-md5 already preloaded from one server to another where the sbcl contrib files have different timestamps. -- Juho Snellman |
From: Vamsee K. <vam...@gm...> - 2007-05-24 06:03:39
|
Juho Snellman wrote: > You're trying to load the sb-rotate-byte contrib (which is a > dependency of sb-md5) multiple times into the same image. That should > not be happening. The only ways I can imagine that happening would be > due to using the :force t argument for asdf:load-op, or some really > baroque scenarios involving transferring core files with sb-md5 > already preloaded from one server to another where the sbcl contrib > files have different timestamps. > Thanks a lot for the reply, in my case I'm guessing it's the first case. I don't use sb-rotate-byte in my code directly, but two of the libraries that I'm using use it. One is ironclad, and the .asd file looks normal enough - I can see this in defsystem: #+sbcl :depends-on #+sbcl (sb-rotate-byte) But the other library, cl-utilities uses this in it's .asd file: ;; Sometimes we can accelerate byte rotation on SBCL by using the ;; SB-ROTATE-BYTE extension. This loads it. #+sbcl (eval-when (:compile-toplevel :load-toplevel :execute) (handler-case (progn (require :sb-rotate-byte) (pushnew :sbcl-uses-sb-rotate-byte *features*)) (error () (delete :sbcl-uses-sb-rotate-byte *features*)))) My lisp-fu is not advanced enough to see if the latter is a problem, but could there be a problem with it? If yes, how can I fix it? Thanks much, Vamsee. |