[omniORB] Name service problem between release and debug versions (20000822)

Sai-Lai Lo S.Lo@uk.research.att.com
23 Aug 2000 16:04:09 +0100


I don't know what you mean by debug and release mode. 

Try remove the trailing '/' in the context name:

$ nameclt list
test.my_context/

$ nameclt list test.my_context/
list: InvalidName exception

$ nameclt list test.my_context
anyExample.Object
ExampleEcho.Object
Echo.Object

Sai-Lai

>>>>> Laurent Pointal writes:

> WinNT 4+SP5
> VC++5+SP3, 
> OmniORB2  built from omniORB3-20000822.tar.gz
> OmniORBpy built from omniORBpy-20000822.tar.gz

> I have a C++ server and a Python client.
> The client reach the server via the NameService (omniNames from OmniORB
> 2.7.1 on another computer).

> Works well in debug mode.
> In release mode I get Invalid name exception.

> With nameclt, "nameclt" list gives me the list from root context, but
> "nameclt list <copy/paste element of root context>" return an Invalid name
> exception.

> An idea?


-- 
Sai-Lai Lo                                   S.Lo@uk.research.att.com
AT&T Laboratories Cambridge           WWW:   http://www.uk.research.att.com 
24a Trumpington Street                Tel:   +44 1223 343000
Cambridge CB2 1QA                     Fax:   +44 1223 313542
ENGLAND