[omniORB] MFC DLL related crash..

[Steven W. Brenneis]

There is not really enough information in your post to form a complete idea of
the problem, but I will give you the standard solutions to MFC/omniORB problems.

Be sure that you are not mixing debug and release shared libraries in your
release build.  This can cause a number of heap allocation problems as well as
problems with the API.

Be sure you are not invoking methods which will attempt to access MFC window and
thread objects from a non-MFC thread (or from any thread that didn't create
these objects for that matter).  MFC disallows access of some MFC objects from
foreign threads.

Good luck, hope this helps.

"Bhatia, Neeraj" wrote:

>         Hi All,
>
>         I am working on a large size application. We decided to use omniORB
> in our development.
>         I have run into a problem. I've gone thru' the problems reported in
> the mail-archives, but
>         not found any solution yet.
>
>         Problem
>         After using the omniORB connection to transfer the data from Tru64
> UNIX to PC (WinNT 4.0),
>         I get a crash only in release mode.
>
>         The crash shows up in NtReplyWaitReceivePortEx which is NT internal
> function.
>
>         Environment
>         Client - PC WinNT 4.0 (SP4)
>         Server - Tru64 Unix
>         OmniORB - Version 2.80
>
>         Description
>         The CORBA interface is provided by a shared library (called
> Interface), available as a
> Win32-DLL in Windows and as a shared library in Unix.
>
>         The client application is written using MFC. It uses a MFC based DLL
> which calls our API (Interface)
> which calls CORBA functions.
>
>         MFC/APP --->  MFC/DLL  --->  Win32/DLL   ----> omniORB/DLL
>                                                 (called Interface)
>         Thanks in advance.
>
>         Regards.
>
>         Neeraj Bhatia
>         COMPAQ Services