[tbnl-devel] New versions 0.11.1 (TBNL) and 0.3.2 (Hunchentoot)
Both new versions (try to) add better debugging capabilities - see http://weitz.de/tbnl/#*catch-errors-p* Cheers, Edi.
On Thu, 14 Sep 2006 16:53:15 -0400, "Erik Enge" <erik.enge@gmail.com> wrote:
Wonderful addition, can't wait to try it out.
Yes, please test. I've only tried with LispWorks, but as I use INVOKE-DEBUGGER I'm pretty confident that it should work equally well with other Lisps.
On 9/15/06, Edi Weitz <edi@agharta.de> wrote:
Yes, please test. I've only tried with LispWorks, but as I use INVOKE-DEBUGGER I'm pretty confident that it should work equally well with other Lisps.
It works on SBCL 0.9.13 on Linux x86, thanks. Though I get this error after terminating the TBNL thread: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION SB-BSD-SOCKETS:SOCKET-CLOSE (1)> when called with arguments (#<SB-SYS:FD-STREAM for "a constant string" {A9BD981}>). [Condition of type SIMPLE-ERROR] Erik.
On Fri, 15 Sep 2006 09:47:29 -0400, "Erik Enge" <erik.enge@gmail.com> wrote:
It works on SBCL 0.9.13 on Linux x86, thanks. Though I get this error after terminating the TBNL thread:
There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION SB-BSD-SOCKETS:SOCKET-CLOSE (1)> when called with arguments (#<SB-SYS:FD-STREAM for "a constant string" {A9BD981}>). [Condition of type SIMPLE-ERROR]
Looks like the problem with SBCL and KMRCL that was already mentioned on this mailing list. You usually don't see this because of IGNORE-ERRORS. That probably means that with an unpatched KMRCL your sockets are never closed...
[Added Kevin to recipient list.] On 9/15/06, Edi Weitz <edi@agharta.de> wrote:
Looks like the problem with SBCL and KMRCL that was already mentioned on this mailing list. You usually don't see this because of IGNORE-ERRORS. That probably means that with an unpatched KMRCL your sockets are never closed...
Well, that would explain the error I'm seeing every now and then when Apache wants to try now-closed Lisp connections. They're not closed! I'm not completely convinced that kmrcl is in the wrong. CLOSE-ACTIVE-SOCKET seems to me to want a socket as an argument, not a stream. Though I'm confused if that's the case as to why it also doesn't use, say, the CMUCL operator for closing sockets, not streams. Unless the CMUCL CLOSE operator actually works on a socket as well. Kevin, can you clarify, is CLOSE-ACTIVE-SOCKET supposed to work as is in 1.87 with a socket or a stream as an argument? The current condition I'm seeing in TBNL is: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION SB-BSD-SOCKETS:SOCKET-CLOSE (1)> when called with arguments (#<SB-SYS:FD-STREAM for "a constant string" {A9BD981}>). [Condition of type SIMPLE-ERROR] and I'm trying to figure out if a) TBNL shouldn't be passing a stream, or b) kmrcl should accept a stream. Thanks, Erik.
This is highly amusing. We just added that ability to our system last week, since TBNL didn't have it. Time to delete some code! Thanks, Edi. Daniel -----Original Message----- From: tbnl-devel-bounces@common-lisp.net [mailto:tbnl-devel-bounces@common-lisp.net] On Behalf Of Edi Weitz Sent: Thursday, September 14, 2006 1:11 PM To: tbnl-devel@common-lisp.net; tbnl-announce@common-lisp.net Subject: [tbnl-devel] New versions 0.11.1 (TBNL) and 0.3.2 (Hunchentoot) Both new versions (try to) add better debugging capabilities - see http://weitz.de/tbnl/#*catch-errors-p* Cheers, Edi. _______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
participants (3)
-
Daniel Gackle -
Edi Weitz -
Erik Enge