[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
sockets in new win32 clisp ?
- To: clisp-list@ma2s2.mathematik.uni-karlsruhe.de
- Subject: sockets in new win32 clisp ?
- From: Don Cohen <donc@ISI.EDU>
- Date: Fri, 10 Oct 97 21:08:00 PDT
Has anyone had any success with this?
I'm trying to use it in win95.
Here are some samples of my attempts:
> (setf server (lisp::SOCKET-SERVER 2000))
#<SOCKET-SERVER 2000>
;; seems ok
> (setf client (SOCKET-CONNECT 2000))
#<SOCKET-STREAM localhost:2000>
;; isn't this is supposed to wait until accepted?
> (princ "hello" client)
"hello"
> (lisp::socket-wait server 0)
NIL
;; and this ought to return t, right?
;; Otherwise how can you tell whether there's a client trying to connect?
> (SOCKET-SERVER-PORT server)
2000
> (setf client (SOCKET-CONNECT 3000))
*** - Winsock error 0
1. Break>
;; And this one is really strange - error 0 is supposed to mean there
;; was no error, and should be ignored, at least according to
;; http://www.sockets.com/err_lst1.htm#WSABASEERR
;; I thought this should wait for some server to accept.
> (socket-accept server)
;; this waits, as it should, but when I c-c I get
*** - handle_fault error1 !
SIGSEGV cannot be cured. Fault address = 0xFFFFFFFF.
LISP caused an invalid page fault in
module KERNEL32.DLL at 0137:bff9e3bb.
Registers:
EAX=00000001 CS=0137 EIP=bff9e3bb EFLGS=00010286
EBX=00000001 SS=013f ESP=00e6ff8c EBP=00e6ffc8
ECX=043c5781 DS=013f ESI=81570bb4 FS=0f17
EDX=8155d7e8 ES=013f EDI=00000000 GS=22a6
Bytes at CS:EIP:
00 00 00 6a 01 6a 01 e8 54 eb fe ff 89 46 2c 85
Stack dump:
bff9e30b 00000008 815593a4 bff86917 00000000 bff9e30b 00000008 815593a4 00000000 00e6ffa0 00e6fdb8 ffffffff bffb8870 bffb89e0 00000000 81573c04