Hi all, I could now do some more tests on the problem and found the following:
The segfault occures in the client while doing a _narrow on the nameservice. It happens at the "delete _orbid" in Request::get_response, line 1005. The referenced object has been deleted before in ORB::del_invoke; called from ORB::get_invoke_reply, line 2808; called from Request::get_response, line 922. I could figure out that this crash was forced by change of the servers hostname. The server is implemented using VisiBroker, whose nameserver responds the initial "_is_a" with a "location forward" containing its own hostname in the IOR. As we have not been informed of the hostname change and no DNS is available the hostname received could not be looked up. This later on results in the described segfault. I guess the expected reaction in this situation should be an exception. I hope, with this infos somebody is able to reproduce and fix the problem. I'm not so deep inside MICO to know how it should work. Regards Hanspeter Am Freitag, 15. Dezember 2006 09:46 schrieb Hanspeter Halle: > Hi all, > we're using MICO for a client application. The server is written by another > company. It worked fine till now, but in a new installation with an updated > server software our client crashes directly after start. As the core file > gave no usefull information I snooped the TCP traffic between client and > server. This traffic consists of only 2 packages: The first is a "_is_a" > request from the client, the 2nd a "Location forward" response sent by the > server. Directly after that response the link is closed. I can send a pcap > file with the trace on request. It happend with MICO 2.3.11 and 2.3.12. > > Unfortunately I have no access to the installation for further debugging, > so any help will be appreciated > > Hanspeter > _______________________________________________ > 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
