"Carlos Eduardo" <[EMAIL PROTECTED]> writes: > I'm testing your Wireless CORBA implementation, MIwCO, but I had some errors > when I initialize the ab (Access Bridge) and the tb (Terminal Bridge). My > system is mico 2.3.12 with wireless service support. I used debug mode, so, > here is the configuration and the output from debug, results a Segmentation > Fault at both, ab and tb:
Did you also happen to configure with --enable-debug? That would help with tracking this down. > #On the Home Location Agent > HLAIP=192.168.0.102 > HLAPORT=12000 > HLAPREFIX=%c0%a8%00%66 > > hla -ORBIIOPAddr inet:192.168.0.102:12000 -POAImplName MobilitySupport \ > -WATMTerminalPrefix %c0%a8%00%66 What are the contents of your ~/.hlarc file? Based on your later configuration, it should have a single line containing 'carlos-desktop' (without the quotes). > # Only on Terminal Bridge > TBIP=192.168.0.101 > TBIPVER=%04 > TBPORT=12010 > TBNOME=carlos-laptop > TBTAMNOME=%0d > > #~/.miwcoapprc > -ORBTerminalId %04%7f%00%00%01%0dcarlos-desktop > -ORBMTBAddr inet:192.168.0.101:12010 > -ORBInitRef MobileTerminalBridge=<HLA IOR> > > tb -WATMGIOPAddr inet:192.168.0.101:12010 -WATMGTPAddr inet: > 192.168.0.102:12020 \ > -POAImplName MobilitySupport -ORBNoIIOPServer -ORBInitRef \ > NameService=corbaloc::$NSIP:$NSPORT/NameService > tb.ref You need to give the -ORBTerminalId argument also when you start the tb program. Just give it on the command line, don't point the tb to your ~/.miwcoapprc file. And the -ORBTerminalId you have above is wrong. The IP address part is supposed to be what you gave as the -WATMTerminalPrefix of the hla. So it should be %04%c0%a8%00%66%0dcarlos-desktop. > [snipped lots] > IIOP: incoming data from inet:192.168.0.102:12019 > GIOP: incoming Reply from inet:192.168.0.102:12019 for msgid 5 status is 1 > IIOPProxy::pull_invoke: id=0x80a7920, rec = 0x80a60b0 > IIOPProxy::handle_invoke_reply: rec=0x80a60b0) > IIOPProxy::del_invoke: rec = 0x80a60b0 > MICO::IIOPProxy::exec_invoke_reply (obj=0, *req=0xbfded10c, *conn=0x80a2710) > IIOP: server listening on inet:192.168.0.102:12010 IIOP version 1.2 Up to this point things seem to be normal, it finds the naming service and tries to find the event service. Then it starts listening on the GTP port (which isn't logged) and on the GIOP port (which is). > Segmentation fault (core dumped) And then it dies. If you did configure with --enable-debug, a backtrace would be useful. Just run 'gdb ab core' with the core file that the ab dumped. After gdb has started, give the command 'bt' and paste the resulting output here. That should help a lot. > # In the outgoing CDR data, there is a line invoking from name service the > object "EventChannelFactory" > # But in the incoming CDR data, there is a line saying > "...NamingContext/NotFound:1.0...", > # So it can't be found, but, how can I solve this problem????? This is actually somewhat odd. From the code it seems that the event service registers itself properly with the naming service, so if you've started them both, the EventChannelFactory should be found. But that's not important, you don't need the event service to get the system running. > #TerminalBridge > #And the terminal bridge is almost the same, but: > Aborted (core dumped) One reason for this could be that, since you didn't manage to start the access bridge, the terminal bridge dies when trying to connect to it. But if it manages to also get to the part where it starts the GIOP server, then that's not it. -- Jaakko Kangasharju This space intentionally left nonblank _______________________________________________ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
