Connection test failure

[David Chisnall]

Hi Everyone,

The connection.m test has been failing for me intermittently ever since I 
started running the test suite, but today I finally persuaded it to fail in the 
debugger.  I don't really know the NSConnection code very well, but this is the 
back trace:

#0  -[NSException raise] (self=<value optimized out>, 
    _cmd=<value optimized out>) at NSException.m:956
#1  0x00007ffff7a05ba8 in +[NSException raise:format:arguments:] (
    self=<value optimized out>, _cmd=0x7ffff7d2ee90, 
    name=<value optimized out>, format=<value optimized out>, 
    argList=<value optimized out>) at NSException.m:849
#2  0x00007ffff7a05ad8 in +[NSException raise:format:] (
    self=<value optimized out>, _cmd=<value optimized out>, name=Unhandled 
dwarf expression opcode 0x0
)
    at NSException.m:835
#3  0x00007ffff79c9039 in -[NSConnection(Private) _getReplyRmc:] (
    self=0x7fffec000a40, _cmd=0x7ffff7d1fde0, sn=0) at NSConnection.m:3214
#4  0x00007ffff79bb55f in -[NSConnection rootProxy] (self=0x7fffec000a40, 
    _cmd=0x7ffff7e4fe30) at NSConnection.m:1671
#5  0x00007ffff7e4d6b5 in +[Tester connectWithPorts:] (self=0x7ffff7e4fcd0, 
    _cmd=0x7ffff7e4fe70, portArray=0x734ae0) at Connection.m:29
#6  0x00007ffff7a5ed48 in -[NSObject performSelector:withObject:] (
    self=<value optimized out>, _cmd=Unhandled dwarf expression opcode 0x0
) at NSObject.m:1827
#7  0x00007ffff7ada463 in -[NSThread main] (self=Unhandled dwarf expression 
opcode 0x0
) at NSThread.m:720
#8  0x00007ffff7adabe2 in nsthreadLauncher (thread=<value optimized out>)
    at NSThread.m:783
#9  0x00007ffff668c8ba in start_thread (arg=<value optimized out>)
    at pthread_create.c:300
#10 0x00007ffff71f302d in clone ()

It then throws the exception, and the test aborts.  If I turn on the debugging 
stuff, I get this:

2011-03-19 16:37:07.691 connection[21203] Initialising new connection with 
parent (null), <NSConnection: 0x732ac0> local: '',(null) remote '',(null)
  Send: <NSMessagePort 0x6fe350 file name 
/tmp/GNUstepSecure1006/NSMessagePort/ports/21203.1>
  Recv: <NSMessagePort 0x6fd970 file name 
/tmp/GNUstepSecure1006/NSMessagePort/ports/21203.0>
[New Thread 0x7ffff3ccd710 (LWP 21208)]
2011-03-19 16:37:07.711 connection[21203] Initialising new connection with 
parent (null), <NSConnection: 0x7fffec0009e0> local: '',(null) remote '',(null)
  Send: <NSMessagePort 0x6fd970 file name 
/tmp/GNUstepSecure1006/NSMessagePort/ports/21203.0>
  Recv: <NSMessagePort 0x6fe350 file name 
/tmp/GNUstepSecure1006/NSMessagePort/ports/21203.1>
2011-03-19 16:37:07.711 connection[21203] Waiting for reply sequence 0 on 
<NSConnection: 0x7fffec0009e0> local: '',<NSMessagePort 0x6fe350 file name 
/tmp/GNUstepSecure1006/NSMessagePort/ports/21203.1> remote '',<NSMessagePort 
0x6fd970 file name /tmp/GNUstepSecure1006/NSMessagePort/ports/21203.0>
2011-03-19 16:37:07.711 connection[21203] handling packet of type 2 (root proxy 
request)
2011-03-19 16:37:07.711 connection[21203]   connection is <NSConnection: 
0x732ac0> local: '',<NSMessagePort 0x6fd970 file name 
/tmp/GNUstepSecure1006/NSMessagePort/ports/21203.0> remote '',<NSMessagePort 
0x6fe350 file name /tmp/GNUstepSecure1006/NSMessagePort/ports/21203.1>



From the fact that this test only fails sometimes, my guess would be that it's 
a problem with the timeout - sometimes it's waiting long enough for the reply, 
sometimes it isn't.  Perhaps someone who understands the things that this class 
is doing with the run loop could take a look?

David