Re: An interesting deadlock in ORBit2...
- From: Justin Schoeman <justin expertron co za>
- To: Michael Meeks <michael ximian com>
- Cc: orbit <orbit-list gnome org>
- Subject: Re: An interesting deadlock in ORBit2...
- Date: Mon, 08 Dec 2003 18:08:05 +0200
Michael Meeks wrote:
> Hi Justin,
>
> On Mon, 2003-12-08 at 07:14, Justin Schoeman wrote:
>
>>Hmmm... I did not realise that I needed to start up a glib mainloop in
>>the CORBA client... Is CORBA_ORB_init() sufficient to start the main
>>loop? If so, then this is not the problem, as CORBA_ORB_init() is
>>called before any threads are started.
>
>
> Nope; you need to do either a CORBA_ORB_run in 1 thread, or run a
> g_main loop elsewhere.
Looking at it some more, this really makes no sense... Do I really have
to fire off a separate thread to run a glib mainloop in the client?
Obviously we can't do it from the parent thread, as this actually does
the client ops. Also, how do you handle locking so that you only begin
client operations after the CORBA_ORB_run() has begun? This really
doesn't make much sense to me...
-justin
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]