This is what I found:

there is a first error (could not find system :aw while constructing a
file-path) which invokes the debugger, followed by a second, timeout
error.

Here is what I see in slime:

component "aw" not found
   [Condition of type ASDF:MISSING-COMPONENT]

Restarts:
 0: [TERMINATE-THREAD] Terminate this thread (#<THREAD "Request
prelude" RUNNING {11EE13D1}>)

Backtrace:
  0: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN)) #<FUNCTION (LAMBDA #)
{119F9DAD}>)
  1: (SWANK::DEBUG-IN-EMACS component "aw" not found)
  2: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION
SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {11F7D2E5}>)
  3: (SWANK::CALL-WITH-BINDINGS ..)
  4: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {121C7C19}>
#<CLOSURE (LAMBDA #) {11F7D2E5}>)
  5: (SWANK:INVOKE-SLIME-DEBUGGER component "aw" not found)
  6: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION
SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {11F7D2C5}>)
  7: (SWANK:SWANK-DEBUGGER-HOOK component "aw" not found #<unavailable
argument>)
  8: (INVOKE-DEBUGGER component "aw" not found)
  9: ((FLET #:LAMBDA13) component "aw" not found)
 10: (SIGNAL component "aw" not found)[:EXTERNAL]
 11: (ERROR ASDF:MISSING-COMPONENT)[:EXTERNAL]
 12: (ASDF:FIND-SYSTEM AW::AW T)
 13: (WEBLOCKS:ASDF-SYSTEM-DIRECTORY AW::AW)
 14: (WEBLOCKS:COMPUTE-PUBLIC-FILES-PATH AW::AW #<unavailable
argument>)
 15: (AW::MAKE-PHOTOS-WIDGET)
 16: (AW::MAKE-MAIN-PAGE)
 17: (AW::INIT-USER-SESSION #<WEBLOCKS:WIDGET "root">)



If I do nothing, it is followed a few seconds later by:



Timeout occurred.
   [Condition of type TIMEOUT]

Restarts:
 0: [CONTINUE] Continue
 1: [ABORT] Return to sldb level 1.
 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "Request
prelude" RUNNING {120B2A49}>)

Backtrace:
  0: ("bogus stack frame")
  1: ("foreign function: pthread_cond_wait")
  2: ("foreign function: lutex_wait")
  3: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CONDITION-WAIT]172))
  4: (SB-THREAD:CONDITION-WAIT ..)
  5: (SB-THREAD:CONDITION-WAIT ..)[:EXTERNAL]
  6: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-MUTEX]267))
  7: (SB-THREAD::CALL-WITH-MUTEX ..)
  8: ((LAMBDA (SWANK-BACKEND::TEST &OPTIONAL SWANK-BACKEND::TIMEOUT))
#<CLOSURE (LAMBDA #) {1223E34D}> NIL)
  9: (SWANK::WAIT-FOR-EVENT (OR (:EMACS-REX . SWANK::_) (:SLDB-RETURN
2)) NIL)
 10: (SWANK::SLDB-LOOP 1)
 11: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN)) #<FUNCTION (LAMBDA #)
{119F9DAD}>)
 12: (SWANK::DEBUG-IN-EMACS component "aw" not found)


The javascript in weblocks.js only knows the timeout symptom, so in
the browser, all you see is the ajax handler in weblocks.js carping
about a timeout.

I have annotated your paste with a version of aw.lisp that compiles,
and also the aw.sbclrc that I used (in conjunction with the directory
setup thru weblocks-intaller).

-- Nandan

--

You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en.


Reply via email to