[comp.windows.x] X and sockets

coltoff@PRC.Unisys.COM (Joel Coltoff) (01/10/89)

My X interface contains BSD socket code that is giving me problems.
It appears to be related to R3. The code was working without any glitches
under R2. When I switched over to R3 and got rid of the X related core
dumps it stopped working. The behavior that I am seeing is that after
a few hundred bytes (< 500) are passed from the application to the interface
the program hangs. The same code compiled and run under R2 works just
as it did before. If I force a core dump and then run dbx the code
is blocked on a select(). This select() is redundant because it is
in a routine that was registered with XtAddInput(). It stays there
because the same module is used to receive data at the other end where
I don't have the benefit of XtAddInput(). In any case it shouldn't hurt.
Does anyone have any idea what is going on here?

Thanks in advance.
-- 
	- Joel
		{psuvax1,sdcrdcf}!burdvax!coltoff	(UUCP)
		coltoff@burdvax.prc.unisys.com		(ARPA)