Error with log-message

[Slobodan Milnović]

Hi,

I'm using:
sbcl 1.0.53
latest quicklisp
hunchentoot 1.2.0 (quicklisp repository)
weblocks 20110829 (quicklisp repository)

Steps to error:

In slime:

CL-USER> (ql:quickload "weblocks")
To load "weblocks":
Load 1 ASDF system:
weblocks
; Loading "weblocks"
............
("weblocks")
CL-USER> (weblocks:start-weblocks :port 8080 :address "127.0.0.1")

Upon connecting to localhost:8080, slime reports an error, and when I
quit the debugger, I get on the webpage the following:

Internal Server Error

An error occured while processing your / request.
Error Message

The function WEBLOCKS::LOG-MESSAGE is undefined.
Backtrace

0: (SB-DEBUG::MAP-BACKTRACE
#<CLOSURE (LAMBDA #) {100318EC2B}>
:START
0
:COUNT
4611686018427387903)
1: (BACKTRACE 4611686018427387903 #<SB-IMPL::STRING-OUTPUT-STREAM {100318EB63}>)
2: (TRIVIAL-BACKTRACE:PRINT-BACKTRACE-TO-STREAM
#<SB-IMPL::STRING-OUTPUT-STREAM {100318EB63}>)
3: (HUNCHENTOOT::GET-BACKTRACE)
4: ((FLET #:LAMBDA769) #<UNDEFINED-FUNCTION LOG-MESSAGE {100316E113}>)
5: (SIGNAL #<UNDEFINED-FUNCTION LOG-MESSAGE {100316E113}>)
6: (ERROR UNDEFINED-FUNCTION :NAME WEBLOCKS::LOG-MESSAGE)
7: (SB-KERNEL::UNDEFINED-FUN-ERROR-HANDLER
#<unavailable argument>
#.(SB-SYS:INT-SAP #X7FFFF66E60C0)
#<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X7FFFF66E5BC0 :TYPE (*
(STRUCT

SB-VM::OS-CONTEXT-T-STRUCT))>
(21))
8: (SB-KERNEL:INTERNAL-ERROR
#.(SB-SYS:INT-SAP #X7FFFF66E5BC0)
#<unavailable argument>)
9: ("foreign function: call_into_lisp")
10: ("foreign function: funcall2")
11: ("foreign function: interrupt_internal_error")
12: ("foreign function: #x41212B")
13: ("bogus stack frame")
14: ((SB-PCL::FAST-METHOD HUNCHENTOOT:ACCEPTOR-DISPATCH-REQUEST
(HUNCHENTOOT:EASY-ACCEPTOR T))
#<unavailable argument>
#S(SB-PCL::FAST-METHOD-CALL
:FUNCTION #<FUNCTION #>
:PV NIL
:NEXT-METHOD-CALL NIL
:ARG-INFO (2))
#<WEBLOCKS:WEBLOCKS-ACCEPTOR (host 127.0.0.1, port 8080)>
#<HUNCHENTOOT:REQUEST {1003135403}>)
15: ((SB-PCL::FAST-METHOD HUNCHENTOOT:HANDLE-REQUEST
(HUNCHENTOOT:ACCEPTOR HUNCHENTOOT:REQUEST))
#<unavailable argument>
#<unavailable argument>
#<WEBLOCKS:WEBLOCKS-ACCEPTOR (host 127.0.0.1, port 8080)>
#<HUNCHENTOOT:REQUEST {1003135403}>)
16: ((SB-PCL::FAST-METHOD HUNCHENTOOT:PROCESS-REQUEST (T))
#<unavailable argument>
#<unavailable argument>
#<HUNCHENTOOT:REQUEST {1003135403}>)
17: (HUNCHENTOOT::DO-WITH-ACCEPTOR-REQUEST-COUNT-INCREMENTED
#<WEBLOCKS:WEBLOCKS-ACCEPTOR (host 127.0.0.1, port 8080)>
#<CLOSURE (LAMBDA #) {100675A87B}>)
18: ((SB-PCL::FAST-METHOD HUNCHENTOOT:PROCESS-CONNECTION
(HUNCHENTOOT:ACCEPTOR T))
#<unavailable argument>
#<unavailable argument>
#<WEBLOCKS:WEBLOCKS-ACCEPTOR (host 127.0.0.1, port 8080)>
#<USOCKET:STREAM-USOCKET {1005A07E43}>)
19: ((SB-PCL::FAST-METHOD HUNCHENTOOT:PROCESS-CONNECTION
(WEBLOCKS:WEBLOCKS-ACCEPTOR T))
#<unavailable argument>
#S(SB-PCL::FAST-METHOD-CALL
:FUNCTION #<FUNCTION #>
:PV NIL
:NEXT-METHOD-CALL NIL
:ARG-INFO (2))
#<WEBLOCKS:WEBLOCKS-ACCEPTOR (host 127.0.0.1, port 8080)>
#<USOCKET:STREAM-USOCKET {1005A07E43}>)
20: ((SB-PCL::FAST-METHOD HUNCHENTOOT:PROCESS-CONNECTION :AROUND
(HUNCHENTOOT:ACCEPTOR T))
#<unavailable argument>
#S(SB-PCL::FAST-METHOD-CALL
:FUNCTION #<FUNCTION #>
:PV NIL
:NEXT-METHOD-CALL #S(SB-PCL::FAST-METHOD-CALL
:FUNCTION #
:PV NIL
:NEXT-METHOD-CALL NIL
:ARG-INFO (2))
:ARG-INFO (2))
#<WEBLOCKS:WEBLOCKS-ACCEPTOR (host 127.0.0.1, port 8080)>
#<USOCKET:STREAM-USOCKET {1005A07E43}>)
21: ((LAMBDA ()))
22: ((LAMBDA ()))
23: ((FLET #:WITHOUT-INTERRUPTS-BODY-[BLOCK412]417))
24: ((FLET SB-THREAD::WITH-MUTEX-THUNK))
25: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-MUTEX]309))
26: (SB-THREAD::CALL-WITH-MUTEX
#<CLOSURE (FLET SB-THREAD::WITH-MUTEX-THUNK) {7FFFF66E6CEB}>
#<SB-THREAD:MUTEX "thread result lock"
owner: #<SB-THREAD:THREAD "hunchentoot-worker-127.0.0.1:50362" RUNNING
{1005A1F4C3}>>
#<SB-THREAD:THREAD "hunchentoot-worker-127.0.0.1:50362" RUNNING
{1005A1F4C3}>
T)
27: (SB-THREAD::INITIAL-THREAD-FUNCTION)
28: ("foreign function: call_into_lisp")
29: ("foreign function: new_thread_trampoline")
Hunchentoot 1.2.0 running on SBCL 1.0.53

My guess is that the error is related to the change in the latest
hunchentoot with the log messaging, as is described in the

http://xach.livejournal.com/284650.html?thread=702186#t702186

[lowmodern]

The easiest way to quickly fix this is probably to change LOG-MESSAGE
to LOG-MESSAGE* in weblocks code.
There are more subtle incompatible changes that affect weblocks, I'll
post later on them.

On Nov 16, 8:45 pm, Slobodan Milnović <slobodan.milno...@gmail.com>
wrote:

[Slobodan Milnović]

2011/11/21 lowmodern <lowm...@gmail.com>:

> The easiest way to quickly fix this is probably to change LOG-MESSAGE
> to LOG-MESSAGE* in weblocks code.
> There are more subtle incompatible changes that affect weblocks, I'll
> post later on them.

Hi,

So, what you're saying is that I should perhaps leave alone the latest
hunchentoot for the time being, and wait for the support implemented
in the weblocks code?

It's not as if I have a need of the latest features, I have just tried
it to see if my small app will work.