[omniORB] Question concerning problems with an old omniORB-version

[Duncan Grisby]

On Monday 7 August, mrfynn at gmx.net wrote:

[...]
> 3. Destroying the clients orb.
> 
> 4. Closing client application by returning 0.
> 
> Only when the application is doing step 2 the system crash occurs, but
> only after the client application is closed (after Step 4).

It's not totally clear from your message which program crashes, the
server on the embedded system or the Windows client. I think you're
talking about the server are you?

If possible, run both client and server with -ORBtraceLevel 25 to see
what they think is going on.

I assume that the network connection is not being closed by orb
destruction, but only happens when the client exists.

One wild guess is that your new compile options mean you no longer have
thread safe C++ exception handling. When the client connection goes
away, the server will throw an exception that should be caught higher up
the call chain. If the exception handling is broken, that could cause a
crash.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --