Re: An interesting deadlock in ORBit2...

[Michael Meeks <michael ximian com>]

Hi Justin,

On Tue, 2003-12-09 at 07:21, 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).

	Ok; I just went over that again, and since we know the client is
polling for us we should never poke the wakeup pipe; I also set NONBLOCK
on the pipe as well ( the missing piece from the last fix ).

	So; HEAD should fix that nicely now, if you update.

> 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 :-(

	Wow - that's extraordinarily vicious; if you run with --g-fatal-errors
(there is some way to get them to bomb out), perhaps we can get some
core dumps that we can use to fix this;

	Thanks,

		Michael.

-- 
 michael@ximian.com  <><, Pseudo Engineer, itinerant idiot