[omniORB] abort problem with thread

[Duncan Grisby]

On Monday 14 May, kexin li wrote:

> In my application, I use thread mutex and condition
> variable in omniORB303 with c++ mapping. The task is
> simple. main process create three threads to connect
> to remote object, main process block on condition
> variable untill all the three threads finished their
> task. But sometimes main process abort with no reason.
> Because the task of remote object which thread invoked
> is very time consumming(it takes around 1 or 2 hours),
> I am wondering is it possible that process  will abort
> if thread of omniORB application idle for a too long
> time?

omniORB won't ever abort without printing a reason why. It must be
something else, perhaps an uncaught exception/

> How can I trace the reason of abort? Can I catch it
> with exception? 

Run your program under a debugger. Then you'll be able to look at a
stack trace when it aborts.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --