Uwe Kindler
2010-04-06 14:28:47 UTC
Hello,
I managed to build omniORB 4.1.4 with MinGW GCC 4.4.0 and MSYS 1.0.11
with this patch applied
http://www.omniorb-support.com/pipermail/omniorb-list/2009-August/030241.html.
I can run the tests eg1 and eg2 successfully. For the example eg3 the
naming service is required. I can start omniNames.exe and eg3_impl.exe
without any problems. If I run eg3_clt.exe now, then it runs to
completion without any errors (It prints ten times: The Echo object
replied, "Hello!"). But running eg3_clt.exe causes omniNames.exe to
crash with the following error:
terminate called after throwing an instance of
'omni::giopStream::CommFailure'
terminate called recursively
I also downloaded the binary distribution of omniORB for VS9 and ran the
eg3 examples (build with MinGW) with the omniNames.exe from this
distribution and the VS9 omniNames.exe did not crash. So it seems there
is a problem with my MinGW built omniNames.exe
Did someone else discovered such a problem with MinGW or does this
indicate that I missed something in the omniNames.exe build process? Any
idea how to solve this before I start debugging?
Best regards,
Uwe Kindler
I managed to build omniORB 4.1.4 with MinGW GCC 4.4.0 and MSYS 1.0.11
with this patch applied
http://www.omniorb-support.com/pipermail/omniorb-list/2009-August/030241.html.
I can run the tests eg1 and eg2 successfully. For the example eg3 the
naming service is required. I can start omniNames.exe and eg3_impl.exe
without any problems. If I run eg3_clt.exe now, then it runs to
completion without any errors (It prints ten times: The Echo object
replied, "Hello!"). But running eg3_clt.exe causes omniNames.exe to
crash with the following error:
terminate called after throwing an instance of
'omni::giopStream::CommFailure'
terminate called recursively
I also downloaded the binary distribution of omniORB for VS9 and ran the
eg3 examples (build with MinGW) with the omniNames.exe from this
distribution and the VS9 omniNames.exe did not crash. So it seems there
is a problem with my MinGW built omniNames.exe
Did someone else discovered such a problem with MinGW or does this
indicate that I missed something in the omniNames.exe build process? Any
idea how to solve this before I start debugging?
Best regards,
Uwe Kindler