Re: An interesting deadlock in ORBit2...

[Justin Schoeman <justin expertron co za>]

Ouch. I just tried creating a glib mainloop in my clients, and the 
results are fairly ugly... Sporadically hangs up waiting for client 
responses, sometimes generates errors like 'OOB incoming msg header 
data', and sometimes causes memory corruption... Unfortunately these are 
rather unpredictable errors.  The memory corruption never seems to 
happed under valgrind, and OOB messages never under gdb.  Very difficult 
to track down exactly what is going wrong here :-(

-justin

Justin Schoeman wrote:
> I will have to look into starting a separate glib mainloop.  The 
> deadlock still occurs in 2.9.2... (the call trace is still the same as 
> before).
> 
> -justin
> 
> Michael Meeks wrote:
> 
>> Hi Justin,
>>
>> On Mon, 2003-12-08 at 15:48, Justin Schoeman wrote:
>>
>>> Hmmm... Interesting, I suppose that is why you should read the docs, 
>>> instead of hacking the examples... None of the examples use 
>>> CORBA_ORB_run in the CORBA client ;-)
>>
>>
>>
>>     Interesting; that's true, it shouldn't be necessary in a pure 
>> client -
>> as you say. How odd.
>>
>>
>>> Unfortunately I was in a bit of a hurry, and did not have time to 
>>> save the dump. I am sure it will occur again though, and I will save 
>>> it next time :-)
>>
>>
>>
>>     Great;
>>
>>     Thanks,
>>
>>         Michael.
>>
> 
> _______________________________________________
> orbit-list mailing list
> orbit-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/orbit-list
>