[slime-devel] Can't reconnect to a swank server
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I am running a swank server (from version 2 of the stable distribution of slime) on sbcl (v1.0.9 on FreeBSD 6.2). When I initially connect to the server using slime-connect, everything works fine. However, when I disconnect, I get a whole dump of diagnostic messages that can be viewed at: http://www.cis.udel.edu/~kamboj/swank-disconnect.txt Now when I try to reconnect to the remote server, I get the following error message: Lisp connection closed unexpectedly: exited abnormally with code 256 I am running the same version of slime on the client and am using xemacs version 21.4.20 on Mac OS X 10.4.10. Any ideas as to what I am doing wrong? Any help would be greatly appreciated. Thanks, Sachin. PS: I have been using slime locally for quite some time and it simply rocks! Thanks! - -- http://www.cis.udel.edu/~kamboj/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHKfOvxGBoJvHBp38RAlc7AJ0ctucHhrqi2nutMRCjDsTdf4uUugCg5dF7 uInAWlTYeJ5/Z3chD/aA9+U= =JhVr -----END PGP SIGNATURE-----
Sachin Kamboj <kamboj@cis.udel.edu> writes:
I am running a swank server (from version 2 of the stable distribution of slime) on sbcl (v1.0.9 on FreeBSD 6.2).
That version is over an year old. Please upgrade to CVS HEAD, and report back if your problem persists. -T.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tobias C. Rittweiler wrote:
Sachin Kamboj <kamboj@cis.udel.edu> writes:
I am running a swank server (from version 2 of the stable distribution of slime) on sbcl (v1.0.9 on FreeBSD 6.2).
That version is over an year old. Please upgrade to CVS HEAD, and report back if your problem persists.
Perhaps it is time for a new stable release? Marijn - -- Marijn Schouten (hkBst), Gentoo Lisp project <http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHMKiap/VmCx0OL2wRAvwfAJ9lk7UHH7DWKySFP/HbN+AdErnVhwCfaym+ s5vjHcnHnFbCfYWr8AXCeAc= =rIbO -----END PGP SIGNATURE-----
"Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:
That version is over an year old. Please upgrade to CVS HEAD, and report back if your problem persists.
Perhaps it is time for a new stable release?
So do I get this right that you're willing to step up as release manager? :-) -T.
On Tue, Nov 06, 2007 at 06:58:36PM +0100, Tobias C. Rittweiler wrote:
"Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:
That version is over an year old. Please upgrade to CVS HEAD, and report back if your problem persists.
Perhaps it is time for a new stable release?
So do I get this right that you're willing to step up as release manager? :-)
is an official release manager really needed ? -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
That version is over an year old. Please upgrade to CVS HEAD, and report back if your problem persists.
Ok, so I upgraded both the client and server to the CVS version. Unfortunately, I still can't reconnect. However, something *has* changed. When I disconnect (using slime-disconnect), the server no longer spits out the previous diagnostic messages. Instead it prints a simple: * ;; swank:close-connection: end of file on #<SB-SYS:FD-STREAM for "a socket" {61716D59}> However, I get the same error at the client: Lisp connection closed unexpectedly: exited abnormally with code 256 Any ideas? Is there anything I could do to help debug the problem? Thanks, Sachin. - -- http://www.cis.udel.edu/~kamboj/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHMMJMxGBoJvHBp38RAl9OAKCPoFCW+WkiugCIQsyPyq5Msu1psgCfRzQT mn8Ygl1w2wLzKfB0FN3Bmfg= =5RKI -----END PGP SIGNATURE-----
Sachin Kamboj <kamboj@cis.udel.edu> writes:
That version is over an year old. Please upgrade to CVS HEAD, and report back if your problem persists.
Ok, so I upgraded both the client and server to the CVS version.
Unfortunately, I still can't reconnect. However, something *has* changed. When I disconnect (using slime-disconnect), the server no longer spits out the previous diagnostic messages. Instead it prints a simple:
Do you set SWANK:*DONT-CLOSE* to T before starting the server? -T.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Do you set SWANK:*DONT-CLOSE* to T before starting the server?
Thanks! That seems to have done the trick... BTW, was there something in the documentation about setting this flag? I think I missed it... - -- http://www.cis.udel.edu/~kamboj/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHMNYQxGBoJvHBp38RAnqgAKDMxiUSII4HWTMbQ24EB5GyENCcBgCfZwA3 UL3uokYy1VyWd2uJUDCpJMA= =7Usi -----END PGP SIGNATURE-----
participants (4)
-
Marijn Schouten (hkBst) -
Sachin Kamboj -
Stelian Ionescu -
Tobias C. Rittweiler