axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] RE: [Gcl-devel] Re: axiom porting


From: Camm Maguire
Subject: Re: [Axiom-developer] RE: [Gcl-devel] Re: axiom porting
Date: 05 May 2005 10:25:45 -0400
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

Greetings!

"Mike Thomas" <address@hidden> writes:

> Hi Bill/Camm.
> 
> | >OK, I've just tested on Linux under ANSI, and it works the same for
> | >me (as it should).  If this is not the case on Windows, please someone
> | >let me know asap.
> | >
> | >
> | Perhaps Mike's test demonstrates that this is not working on the
> | Windows ANSI version, but it works fine for me on Windows XP
> | with the non-ANSI version.
> 
> I just tried the CLtL1 build - no joy.
> 

OK, at least we have some consistency.

> There are definite problems with the new code as socket variables should be
> defined with SOCKET (an unsigned int) rather than int and the error return
> values on Windows are not the same as on BSD systems however I just tried to
> eliminate those problems and still have the same trouble.
> 

This could be the problem, but I'd be skeptical, as you had success
earlier.  The accept error message reports the C strerror string,
which was "No such file ..."  I think this is the first of the
following errors, whatever mingw's numbering system could be:

ERRORS
       EAGAIN or EWOULDBLOCK
              The  socket  is  marked non-blocking and no connec-
              tions are present to be accepted.

       EBADF  The descriptor is invalid.

       ENOTSOCK
              The descriptor references a file, not a socket.

       EOPNOTSUPP
              The referenced socket is not of type SOCK_STREAM.

       EFAULT The addr parameter is not in a writable part of the
              user address space.

       EPERM  Firewall rules forbid connection.

       ENOBUFS, ENOMEM
              Not  enough free memory.  This often means that the
              memory allocation is limited by the  socket  buffer
              limits, not by the system memory.



Sounds to me that #'listen is returning T before a connection is
present, i.e. the select code we've added there might not be working
for you.  Just an idea.  

> I'm using Internet Explorer.  I'll keep looking perhaps tomorrow.  Hopefully
> this is due to a stupid mistake on my part.
> 

Might want to start with telnet for simplicity.  Might want to break
in gdb at the select in #'listen, and see if it is working, and if so,
whether it is accept that fails for some other reason.

Take care,

> Cheers
> 
> Mike Thomas.
> 
> 
> 
> 
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah




reply via email to

[Prev in Thread] Current Thread [Next in Thread]