From: Chun T. (binghe) <bin...@gm...> - 2008-10-29 04:42:54
Attachments:
SBCL-CLOS-BUG.txt
|
Hi, SBCL Yesterday I try to compile a DEFCLASS with a slot's TYPE as (SATISFIES THREADP), and got a wired error: debugger invoked on a SB-INT:BUG: failed AVER: "(NOT (FUNCTIONAL-HAS-EXTERNAL-REFERENCES-P CLAMBDA))" This is probably a bug in SBCL itself. (Alternatively, SBCL might have been corrupted by bad user code, e.g. by an undefined Lisp operation like (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe Lisp code; or there might be a bug in the OS or hardware that SBCL is running on.) If it seems to be a bug in SBCL itself, the maintainers would like to know about it. Bug reports are welcome on the SBCL mailing lists, which you can find at <http://sbcl.sourceforge.net/>. After remove the TYPE part, compile resume OK. I cannot reproduce it today, strange, so I put the full backtrace in attach, maybe anyone who can understand what's wrong happened here. Regards, Chun Tian (binghe) |
From: Nikodemus S. <nik...@ra...> - 2008-11-04 10:50:25
|
On Wed, Oct 29, 2008 at 6:42 AM, Chun Tian (binghe) <bin...@gm...> wrote: > Yesterday I try to compile a DEFCLASS with a slot's TYPE as (SATISFIES > THREADP), and got a wired error: > > debugger invoked on a SB-INT:BUG: > failed AVER: "(NOT (FUNCTIONAL-HAS-EXTERNAL-REFERENCES-P CLAMBDA))" > This is probably a bug in SBCL itself. (Alternatively, SBCL might have been > corrupted by bad user code, e.g. by an undefined Lisp operation like > (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe > Lisp code; or there might be a bug in the OS or hardware that SBCL is > running > on.) If it seems to be a bug in SBCL itself, the maintainers would like to > know about it. Bug reports are welcome on the SBCL mailing lists, which you > can find at <http://sbcl.sourceforge.net/>. > > After remove the TYPE part, compile resume OK. > > I cannot reproduce it today, strange, so I put the full backtrace in attach, > maybe anyone who can understand what's wrong happened here. No immediate ideas. If you manage to reproduce this, I would dearly love seeing the source that causes this to happen. Cheers, -- Nikodemus |