Menu

Posix sockets changed or broken?

Help
2001-03-10
2001-04-25
  • Sean Cavanaugh

    Sean Cavanaugh - 2001-03-10

        I've managed to get my project to the point where it will compile and link against both the Win32 and Posix trees (latest CVS) with no modifications.  However I have a new problem:  The posix version on Linux x86 (Debian) however does not run correctly.  It aparently cannot correctly bind a socket for listening (when run as a server) or connect to a working server (when run as a client).  As far as the application is concerned it is receiving no error results from CommonC++ and it thinks it is working properly.

        Most of the changes I've needed in CommonC++ itself were in the Win32 tree to get everything working right there, but now I am mysteriously broken on the posix side and am kind of baffled by it.

     
    • David Sugar

      David Sugar - 2001-03-12

      A quick check with the demo tcpthread indicates it still is working on
      my machine (Mandrake, not Debian...).  Does even the "tcpthread" demo app fail to bind a socket (localhost:4096) for you?

       
      • Sean Cavanaugh

        Sean Cavanaugh - 2001-04-25

        It turns out it looks like the timeout_t value of 0 has become an infinite timeout?  I was using the value 0 before to signify a non-blocking test, of which I've changed it to the value 1 instead to fix everything . . .

         

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.