Yes, still cores. Debug output below. Thanks -Chuck
naming$ ./tellabs-client.exe
Using 0 as a concurrency model of whole orb.
Using thread-pool concurrency model.
Using client concurrency model: threaded
MICO::InputHandler::InputHandler()
ActiveMsgQueue::ActiveMsgQueue(): (0xb57288)
MICO::MTDispatcher::MTDispatcher()
ActiveMsgQueue::ActiveMsgQueue(): (0xb57720)
IIOP: server listening on inet:0.0.0.0:1706 IIOP version 1.0
binding to inet:10.119.2.131:1706
void_array::__fast_insert (0xb57f00): return 0
ORB::add_invoke (MsgId=2)
IIOP: making new GIOP 1.0 connection to inet:10.77.83.35:3075
GIOPCodec::GIOPCodec(): 0xb55f78
MICO::GIOPConnReader::GIOPConnReader(0xb55fe0)
GIOP: Codeset negotiation with inet:10.77.83.35:3075 using GIOP version 1.0
MICO::GIOPConnReader::_run()
GIOP: sending Request to inet:10.77.83.35:3075 msgid is 2
IIOPProxy::add_invoke: rec=0xb58af8, id=0xb56850, msgid=2)
MICO::GIOPConn::output (CORBA::Buffer *b)
b: 0xb58888
Out Data 47 49 4f 50 01 00 01 00 58 00 00 00 00 00 00 00 GIOP....X.......
02 00 00 00 01 00 00 00 0b 00 00 00 4e 61 6d 65 ............Name
53 65 72 76 69 63 65 00 06 00 00 00 5f 69 73 5f Service....._is_
61 00 00 00 00 00 00 00 28 00 00 00 49 44 4c 3a a.......(...IDL:
6f 6d 67 2e 6f 72 67 2f 43 6f 73 4e 61 6d 69 6e omg.org/CosNamin
67 2f 4e 61 6d 69 6e 67 43 6f 6e 74 65 78 74 3a g/NamingContext:
31 2e 30 00 1.0.
ORB::wait for 0xb56850
MICO::GIOPConn::input_ready ()
conn: 0xb55fe0
ev: GIOPConnCallback::InputReady
t_mod: 0
pool:
conn:
req:
_activerefs: 2
In Data 47 49 4f 50 01 00 00 01 00 00 00 ca 00 00 00 00 GIOP.......Ê....
00 00 00 02 00 00 00 03 00 00 00 28 49 44 4c 3a ...........(IDL:
6f 6d 67 2e 6f 72 67 2f 43 6f 73 4e 61 6d 69 6e omg.org/CosNamin
67 2f 4e 61 6d 69 6e 67 43 6f 6e 74 65 78 74 3a g/NamingContext:
31 2e 30 00 00 00 00 01 00 00 00 00 00 00 00 86 1.0.............
00 01 02 00 00 00 00 0c 6d 61 72 63 76 69 65 77 ........marcview
65 6d 73 00 0c 03 00 00 00 00 00 36 3a 3e 02 32 ems........6:>.2
31 12 6f 72 62 69 78 45 32 41 2e 2e 6c 6f 63 61 1.orbixE2A..loca
74 69 6f 6e 14 49 54 5f 4e 61 6d 69 6e 67 43 6f tion.IT_NamingCo
6e 74 65 78 74 45 78 74 00 08 00 02 00 00 00 00 ntextExt........
00 00 00 00 00 00 00 02 00 00 00 01 00 00 00 18 ................
00 00 00 00 00 01 00 01 00 00 00 00 00 01 01 04 ................
00 00 00 01 00 01 01 09 00 00 00 06 00 00 00 06 ................
00 00 00 00 00 2c .....,
IIOP: incoming data from inet:10.77.83.35:3075
GIOP: incoming Reply from inet:10.77.83.35:3075 for msgid 2 status is 3
ORB::get_invoke (MsgId=2)
IIOPProxy::pull_invoke: id=0xb56850, rec = 0xb58af8
IIOPProxy::handle_invoke_reply: rec=0xb58af8)
IIOPProxy::del_invoke: rec = 0xb58af8
MICO::IIOPProxy::exec_invoke_reply (obj=0xb557e8, *req=0xb55528, *conn=0xb55fe0)
GIOPConn::deref: 0xb55fe0, refcnt: 1, activerefs: 2
ORB::del_invoke (MsgId=2)
ORB::add_invoke (MsgId=3)
Warning: cannot resolve hostname 'marcviewems' into an IP address.
Warning: cannot resolve hostname 'marcviewems' into an IP address.
IIOP: making new GIOP 1.0 connection to inet:marcviewems:3075
Warning: cannot resolve hostname 'marcviewems' into an IP address.
IIOP: connect to inet:marcviewems:3075 failed: invalid address
ORB::wait for 0xb56850
ORB::del_invoke (MsgId=3)
Segmentation fault (core dumped)
naming$
-----Original Message-----
From: Rob Ratcliff [mailto:[EMAIL PROTECTED]
Sent: Friday, July 14, 2006 11:03 AM
To: Irvine, Chuck R [LTD]
Cc: [email protected]
Subject: RE: [mico-devel] Connecting to an Orbix name service
Does it core if you put this flag:
-ORBNoResolve
in your .micorc file?
On Fri, 2006-07-14 at 10:53 -0500, Irvine, Chuck R [LTD] wrote:
> After turning on mico debug output, I discovered the problem. I was
> using a raw ip address rather than a host name to talk to the name
> service. I was using the ip address because the hostname isn't visible
> to my workstation. After inserting an appropriate entry into my
> ect/hosts file, things are working now.
>
> However, I would think that mico shouldn't core dump on this kind of
> error. Thoughts?
>
> Thanks,
> Chuck
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Irvine, Chuck R [LTD]
> Sent: Friday, July 14, 2006 9:49 AM
> To: [email protected]
> Subject: [mico-devel] Connecting to an Orbix name service
>
>
> I'm new to Corba (and Mico) and could sure use a little help ....
>
> I'm writing a Corba client using Mico 2.3.12 which will talk to an
> Orbix 6.x server. First, can anyone verify that this should work?
>
> The first thing I need to do is connect to the Orbix naming service
> and I'm getting a segfault. I'm probably not doing something right. My
> call to "orb->resolve_initial_references ("NameService")" returns
> without error, but when I call "CosNaming::NamingContext::_narrow
> (nsobj)" on the name service object, I get a segfault. I call my code
> thus:
>
> ./get-orbix-name-service -ORBInitRef
> NameService=corbaloc::10.77.83.35:3075/NameService
>
> My sample code is given below. Any help would be hugely appreciated.
>
> Thanks,
> Chuck
>
> --------------get-orbix-name-service--------------------
>
> #include <CORBA.h>
> #include <coss/CosNaming.h>
>
> using namespace std;
>
> int main (int argc, char *argv[])
> {
> // ORB initialization
> CORBA::ORB_var orb = CORBA::ORB_init (argc, argv, "mico-local-orb"
> );
>
> CORBA::Object_var nsobj =
> orb->resolve_initial_references ("NameService");
>
> if (CORBA::is_nil(nsobj)) {
> cerr << "oops, name service is nil" << endl;
> exit(1);
> }
>
> CosNaming::NamingContext_var nc =
> CosNaming::NamingContext::_narrow (nsobj);
>
> if (CORBA::is_nil (nc)) {
> cerr << "oops, I cannot access the Naming Service!" << endl;
> exit (1);
> }
>
> cout << "acquired naming service" << endl;
>
> return 0;
> }
>
> -------------------------------------------------------------
>
>
> _______________________________________________
> Mico-devel mailing list
> [email protected] http://www.mico.org/mailman/listinfo/mico-devel
>
>
>
> _______________________________________________
> Mico-devel mailing list
> [email protected] http://www.mico.org/mailman/listinfo/mico-devel
_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel
