Re: [Evolution-hackers] Progress with... <snip> - ORBit2 event loop is causing the crash

[Not Zed <notzed ximian com>]

Orbit and gthread calls are outside the scope of camel; i have no idea
why they would be crashing, doubtful that camel would have anything to
do with it.  Unless you can't create a gthread reliably from a normal
posix one.  And unless you can't call orb_run without a g_main_loop it's
running under - which again isn't camel.

Camel precludes the use of gobject basically because gobject isn't
threadsafe, if orb_run is also not threadsafe, that is its problem too.

You really need a good backtrace.  Make sure the mono plugin is
de-installed or deactivated, as that will interfere with stack traces.

On Thu, 2005-09-01 at 15:37 +0200, Jules Colding wrote:
> On Thu, 2005-09-01 at 15:08 +0200, Jules Colding wrote:
> > Hi,
> > 
> > I am making progress, but Evolution 2.4 crashes at startup. I can not
> > get a usable backtrace so my guess is that my skeleton Camel store
> > methods are causing the crash by doing something really stupid.
> 
> OK, I've narrowed this down to when I am calling CORBA_ORB_run() in
> camel-brutus-store.c:156. Everything works, except for the fact that I
> can't get an ORB, when CORBA_ORB_run() isn't called. 
> 
> Are there some deep magic that forbids the ORB loop to be invoked in
> Camel?
> 
> Any ideas on how to make this work??
> 
> 
> Thanks,
>   jules
> 
> 
> 
> 
> _______________________________________________
> Evolution-hackers mailing list
> Evolution-hackers gnome org
> http://mail.gnome.org/mailman/listinfo/evolution-hackers
-- 
adfa(evolution-2.4:20087): gtkhtml-WARNING **: cannot find icon:
'stock_insert-url' in gnome