[Bese-devel] Bug?
Friedrich Dominicus
frido at q-software-solutions.de
Tue Aug 9 06:40:04 UTC 2005
Well while trying the new ucw stuff I got this message:
The value (SETF COMPONENT.PLACE) is not of type SYMBOL.
[Condition of type TYPE-ERROR]
Restarts:
0: [SHOW-BACKTRACE] Send the client a backtrace page.
1: [RETRY] Clearout the response and retry calling the action.
2: [SERVER-ERROR] Send the client an internal server error page.
3: [ABORT-RESPONSE] Abort this response and answer another request
4: [TERMINATE-THREAD] Terminate this thread (#<THREAD {1000BB08B1}>)
Backtrace:
0: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT (T)) #<unused argument> #<unused argument> #<FUNCTION (LAMBDA NIL) {1000470029}>)
1: (SWANK::CALL-WITH-BINDINGS ((*PRINT-PRETTY*) (*PRINT-LEVEL* . 4) (*PRINT-LENGTH* . 10) (*PRINT-CIRCLE* . T) (*PRINT-READABLY*) (*PRINT-PPRINT-DISPATCH* . #<SB-PRETTY:PPRINT-DISPATCH-TABLE {1002D921D1}>) (*PRINT-GENSYM* . T) (*PRINT-BASE* . 10) (*PRINT-RADIX*) (*PRINT-ARRAY* . T) ...) #<FUNCTION (LAMBDA NIL) {100046FFC9}>)
2: (SWANK::DEBUG-IN-EMACS #<TYPE-ERROR {1001DE2C71}>)
3: ((SB-PCL::FAST-METHOD IT.BESE.UCW::HANDLE-ACTION-ERROR (ERROR)) #<unavailable argument> #<unavailable argument> #<TYPE-ERROR {1001DE2C71}>)
Has anyone used a multithreaded SBCL with UCW?
Regards
Friedrich
More information about the bese-devel
mailing list