On Mon, Dec 28, 2009 at 02:32:14AM -0600, Peter Keller wrote:
It only happened once for me so far in my testing. Had I known it wasn't easily reproducable, I would have gotten a full backtrace.
It figures I'd get the failure 5 seconds after sending the emai:
0] backtrace
0: (IOLIB.MULTIPLEX::%DISPATCH-EVENT #S(IOLIB.MULTIPLEX::FD-ENTRY :FD 8 :READ-HANDLER NIL :WRITE-HANDLER NIL :ERROR-CALLBACK NIL) :WRITE :ERROR 1478938.390490213d0) 1: (IOLIB.MULTIPLEX::%HANDLE-ONE-FD #<event base, 2 FDs monitored, using: #<epoll(4) multiplexer> {B2080C1}> (8 (:ERROR :READ :WRITE)) 1478938.390490213d0 #<unavailable argument>) 2: (IOLIB.MULTIPLEX::DISPATCH-FD-EVENTS-ONCE #<event base, 2 FDs monitored, using: #<epoll(4) multiplexer> {B2080C1}> 7.825390378013253d0 1478938.390490213d0) 3: ((SB-PCL::FAST-METHOD IOLIB.MULTIPLEX:EVENT-DISPATCH (IOLIB.MULTIPLEX:EVENT-BASE)) #<unavailable argument> #<unavailable argument> #<event base, 2 FDs monitored, using: #<epoll(4) multiplexer> {B2080C1}>)[:EXTERNAL] 4: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-INT:&MORE SB-PCL::.DFUN-MORE-CONTEXT. SB-PCL::.DFUN-MORE-COUNT.)) #<unused argument> #<unused argument> #<event base, 2 FDs monitored, using: #<epoll(4) multiplexer> {B2080C1}> -303312229 2) 5: ((FLET %RUN-SERVER)) 6: (RUN-SERVER :HOST #/ip/0.0.0.0 :PORT 10000 :NEW-PROCESS NIL :TIMEOUT 3600) 7: (SB-INT:SIMPLE-EVAL-IN-LEXENV (RUN-SERVER :PORT 10000 :NEW-PROCESS NIL :TIMEOUT 3600) #<NULL-LEXENV>) 8: (SB-EXT:INTERACTIVE-EVAL (RUN-SERVER :PORT 10000 :NEW-PROCESS NIL :TIMEOUT 3600))[:EXTERNAL] 9: (SB-IMPL::REPL-FUN NIL) 10: ((LAMBDA ())) 11: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA #) {AD29EAD}>) 12: (SB-IMPL::TOPLEVEL-REPL NIL) 13: (SB-IMPL::TOPLEVEL-INIT) 14: ((LABELS SB-IMPL::RESTART-LISP))
-pete