[omniORB] Bidirectional GIOP calls using Endpoints with Omninames

[DESCOMBES Thierry]

Hello,
I'm trying to port omniOrb 3.0.5 to the Etrax platform (a 32bit
processor). All seems to work fine, except that a "segmentation fault"
occurs when I try to get back a reference with an unknown name from the
nameservice. The same code works fine on a Linux PC platform (and raises
a CORBA::SystemException)...
I have run it with the -ORBLevelTrace set to 20.
I really don't understand what append, and how to modify this.
Thanks in advance.
Cheers
Thierry

omniORB: strand Ripper: start.
omniORB: gateKeeper is tcpwrapGK 1.0 - based on tcp_wrappers_7.6
omniORB: The omniDynamic library is not linked.
omniORB: Initialising incoming rope factories.
omniORB: strand Rope::incrRefCount: old value = 0
omniORB: Starting incoming rope factories.
omniORB: scavenger : start.
omniORB: tcpSocketMTfactory Rendezvouser: start.
omniORB: tcpSocketMTfactory Rendezvouser: block on accept()
omniORB: Activating: root<0>
omniORB: Creating ref to local: root<0>
 target id      : IDL:DaqApplication/TTdaqToTTsensorItf:1.0
 most derived id: IDL:DaqApplication/TTdaqToTTsensorItf:1.0
omniORB: strand Rope::incrRefCount: old value = 0
omniORB: Creating ref to remote: key<0x4e616d6553657276696365>
 target id      : IDL:omg.org/CORBA/Object:1.0
 most derived id:
omniORB: Initial reference `NameService' resolved from -ORBInitRef
argument.
omniORB: strand Rope::incrRefCount: old value = 1
omniORB: Creating ref to remote: key<0x4e616d6553657276696365>
 target id      : IDL:omg.org/CosNaming/NamingContext:1.0
 most derived id:
Segmentation fault