Bug in NSRunLoop?

[Marcus Müller]

Hi,

I think I've found a bug in the NSRunLoop but I don't understand why the 
bug occurs. The problem is pretty simple. If you create a socket and 
attach it to the runloop by telling it to -acceptInBackgroundAndNotify, 
the socket will be added to the runloop and all is fine for the first 
connection. The second connection (and any other successive connections) 
doesn't work, however, as it appears that the new socket is 
automatically closed. I don't know why that happens. Unfortunately I 
cannot debug the problem as I'm on FreeBSD and cannot build a debug 
build of GNUstep (compiler [gcc 3.0.4] crashes), but that's another 
story. Can somebody else please investigate?

In order to make debugging easier I've written a testcase. It's 
available at:

http://www.mulle-kybernetik.com/~znek/GNUstep/GSSocketTest.tar.bz2

The testcase runs as expected under Mac OS X but fails with the symptoms 
described above on my FreeBSD box. I suspect that the same will happen 
on any GNUstep platform.

Thanks for your help in advance,

  Marcus

--
Marcus Mueller  .  .  .  crack-admin/coder ;-)
Mulle kybernetiK  .  http://www.mulle-kybernetik.com
Current projects: finger address@hidden