[movitz-devel] Warning: Auto-bootstrapping CLOS completed.

[Paavo Parkkinen]

Here's the backtrace from movitz:

Enter..Ok.
Installing los0-GC with 63238 KB.
Break: Auto-bootstrapping CLOS.
Warning: Auto-bootstrapping CLOS completed.
 0: Return from break: Auto-bootstrapping CLOS.
[0d] LOS0> :bt
 <3 (BREAK "Auto-bootstrapping CLOS.")
 <1 (MUERTE::SIGNAL-SIMPLE SIMPLE-CONDITION NEWLINE NIL)
 <= (SIGNAL NEWLINE)
 <= (X86-PC::TEXTMODE-SCROLL-DOWN)
 <= (X86-PC::TEXTMODE-WRITE-CHAR #\Newline)
 <= (TEXTMODE-CONSOLE MUERTE::STREAM-WRITE-CHAR {ebx unknown})
 <= (MUERTE::%WRITE-CHAR #\Newline #<function TEXTMODE-CONSOLE>)
 <= (WRITE-CHAR #\Newline NIL)
 <= (TERPRI)
 <= (MUERTE::FORMAT-BY-STRING "~&Installing los0-GC with ~D KB.~%" #x0 #x0 NIL)
 <= (FORMAT T "~&Installing los0-GC with ~D KB.~%" #xf706)
 <= (GENESIS)
 <= (MUERTE::|losp/los0.lisp|)
 ...


p

2008/11/10 Frode V. Fjeld <frodef at cs.uit.no>:
> "Paavo Parkkinen" <pparkkin at iki.fi> writes:
>
>> I compiled and dumped the los0 image with SBCL, and booted it with
>> qemu like I've done many times before, only this time I got this:
>>
>> Enter..Ok.
>> Installing los0-GC with 63238 KB.
>> Break: Auto-bootstrapping CLOS.
>> Warning: Auto-bootstrapping CLOS completed.
>>  0: Return from break: Auto-bootstrapping CLOS.
>> [0d] LOS0> 0
>> Warning: CLOS was already bootstrapped: T
>> Warning: Auto-bootstrapping CLOS completed.
>> Error: Out of memory. Please take out the garbage.
>> [0d] LOS0>
>
> There is a bootstrapping of CLOS that is initiated quite early in the
> boot process, but if some method dispatch is triggered before this
> happens, you get the above break. It usually indicates that something
> "bad" or too "complex" happened too early in the boot process.
>
> A stack-trace should tell you/us what is triggering the CLOS bootstrap.
>
> --
> Frode V. Fjeld
>
>
> _______________________________________________
> movitz-devel site list
> movitz-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/movitz-devel
>