|
Hello
Developers Configuration
and Versions: Both C++
(Mico) and Java (JacORB) code are compiled against the same IDL. Mico
Version: 2.3.11 JacORB
Version: 2.2.2 (June 1, 2005) GIOP and
IIOP versions are 1.2, and this information is defined in a .micorc file RedHat
Fedora Core 4 (2.6.11-1) RedHat
Enterprise 4 Update 3 (2.6.9-34) Interface: A C++
application looks-up and gets a CORBA object reference to a Java application. The C++
application uses the CORBA object reference to the Java application to pass a CORBA
object reference of itself to the Java application. The Java
application receives and stores the C++ CORBA object reference. Later,
the Java application uses the stored C++ CORBA object reference to notify the
C++ application of a change. Problem: On
RedHat Enterprise 4 Update 3 (2.6.9-34), as soon as the Java application uses
the stored C++ CORBA object reference to notify the C++ application of a
change, the C++ application dies with a segmentation fault. Using gdb
reveals that the C++ application is dying somewhere in the Mico skeleton/stub
code:
dispatch() which is called by
invoke() which is called by
doinvoke() which is called by
perform_invoke() which is called by
local_invoke() which is called by
invoke_async() which is called by
callback() etc… On
RedHat Fedora Core 4 (2.6.11-1), the C++ application receives the notification
of a change from the Java application and continues running without any
problems. Notes: On
RedHat Enterprise 4 Update 3 (2.6.9-34), where the CORBA interface doesn't
work, we have tried turning up the debug on Mico with -ORBDebugLevel 5,
-ORBDebugLevel 50, and -ORBDebugLevel 5000 but we don't see any debug output
anywhere. Is there any debug? If so, where does it go? On
RedHat Enterprise 4 Update 3 (2.6.9-34), where the CORBA interface doesn't
work, we ran iordump on an IOR and confirmed the GIOP and IIOP versions to be
1.2. On
RedHat Fedora Core 4 (2.6.11-1), where the CORBA interface works, we ran
iordump on an IOR, but it died with a segmentation fault. Thanks, Jeff Dugan |
_______________________________________________ Mico-devel mailing list [email protected] http://www.mico.org/mailman/listinfo/mico-devel
