Connect system call in SCO

[Rakshit Karnavat , Gurgaon]

  Hi Robert,
      think it is the problem with the connect system call itself, when it
fails.
     Or has my system got corrupted.
    I am using FSUPthreads, as the thread support on SCO.
    The example program which confirmed it is attached.
      It is a client program. Just make it fail at the connect system call.
I gave a wrong server IP to
       make it fail. 
  Any hints.
Regards
Rakshit.

      <<client1.cpp>> 


> ----------
> From: 	Robert Lipe[SMTP:robertlipe@usa.net]
> Sent: 	Tuesday, December 11, 2001 10:32 PM
> To: 	Rakshit Karnavat , Gurgaon
> Cc: 	gcc@gcc.gnu.org
> Subject: 	Re: Connect system call in SCO
> 
> >    It is a multithreaded program, using both INET and UNIX domain
> sockets.
> 
> I suspect that's the key clue.  OpenServer doesn't support threads.
> Look at whatever packaging you're using that's dummying up threads.
> That package is presumably responsible for "fixing" errno to make it
> thread-safe.
> 
> >   But it was set to -2146297092(junk probably).
> >     I don't have a clue what this is.
> 
> It may be that your compilatino line isn't turning on whatever manifest
> your thread package is using to wrap errno.
> 
> RJL
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: client1.cpp
Type: application/octet-stream
Size: 1411 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20011213/df9f6b59/attachment.obj>