On Fri, 2004-03-26 at 09:42 +0800, Not Zed wrote:
> Yeah i dunno either. Maybe trylock isn't implemented in valgrind's
> 'hacked pthread lib' (as it calls itself).
Most odd.
> FWIW with this disabled, certain things simply don't work running in
> valgrind. Although they could point to code bugs. When you try to do
> autocompletion, it always complains that its getting stuff out of
> sequence. i.e. i think it gets responses before the call returns.
> (which is definetely a code bug if thats what happens - this is in
> eds/evo code though).
What complaints do we get ? I'd be very suprised if incoming async
replies were happening before the outgoing async method had completed;
but - I suppose it might be possible in some scenarios - if you have a
thread-per-request, or thread-per-connection type policy, then clearly
the kernel could task the async caller out indefinately, while the other
side proccessed / replied, and then task in the thread that handles
incoming stuff, before the outgoing thread completed - that's rather
unavoidable.
Regards,
Michael.
--
[EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution-hackers
