[omniORB] omniNames.exe (MinGW build) crashes on eg3_clt.exe run (part2)

[Uwe Kindler]

Hello,

My omniNames.exe (MinGW build) crashes when example eg3_clt.exe finishes.

I ran eg3_clt.exe in debugger to check when omniNames.exe crashes.
omniNames.exe crashes (returns with exit code 3) when orb->destroy() is
called in eg3_clt.exe as soon as the destructor "inline
~_CORBA_ObjRef_Var()" is entered. This happens only for MinGW build
omniNames.exe.

Any idea why a call to ~_CORBA_ObjRef_Var() in client code may cause
omniNames.exe (MinGW build) to exit with exit code 3?

Best regards,

Uwe Kindler

[Wolfgang Glas]

Hi Uwe,

I'm runnning omniorb-4.1.4 under Win32 and Win64 using the latest
mingw-w64-gcc-4.4.1 distribution from mingw-w64sf.net and encountered no problems.

I use omniNames.exe in a Windows SErver 2003 xs64 production setup and there,
omniNames.exe runs smoothly as a Windows service for weeks...

IMHO you should upgrade your compuiler toolchain to the gcc-4.4.1 version,
because as far as I can remember the gcc-4.4.0 distribution had some serious
problems.

Best regards,

Wolfgang

Post by Uwe Kindler
Hello,
My omniNames.exe (MinGW build) crashes when example eg3_clt.exe finishes.
I ran eg3_clt.exe in debugger to check when omniNames.exe crashes.
omniNames.exe crashes (returns with exit code 3) when orb->destroy() is
called in eg3_clt.exe as soon as the destructor "inline
~_CORBA_ObjRef_Var()" is entered. This happens only for MinGW build
omniNames.exe.
Any idea why a call to ~_CORBA_ObjRef_Var() in client code may cause
omniNames.exe (MinGW build) to exit with exit code 3?
Best regards,
Uwe Kindler
_______________________________________________
omniORB-list mailing list
http://www.omniorb-support.com/mailman/listinfo/omniorb-list

[Uwe Kindler]

Hi Wolfgang,

BINGO!!! I installed GCC 4.4.1 for MinGW and did a complete rebuild of
omniORB and now omniNames.exe does not crash anymore when I run the
eg3_clt.exe example.

You saved me a lot of time and headache - thank you very much. Where
should I send your money ;O)

For all omniORB list readers that use MinGW:

It is not possible to build a working omniORB installation with MinGW
and GCC 4.4.0 (at least for me). Use GCC 4.4.1 instead.

Best regards,

Uwe

Post by Wolfgang Glas
Hi Uwe,
I'm runnning omniorb-4.1.4 under Win32 and Win64 using the latest
mingw-w64-gcc-4.4.1 distribution from mingw-w64sf.net and encountered no problems.
I use omniNames.exe in a Windows SErver 2003 xs64 production setup and there,
omniNames.exe runs smoothly as a Windows service for weeks...
IMHO you should upgrade your compuiler toolchain to the gcc-4.4.1 version,
because as far as I can remember the gcc-4.4.0 distribution had some serious
problems.
Best regards,
Wolfgang