the code in evolution to start up any component is not multithreaded. Jeff
On Mon, 2002-06-24 at 03:48, Jerome Lacoste wrote: > On Mon, 2002-06-24 at 01:30, Jeffrey Stedfast wrote: > > Given that: > > > > 1. Evolution works fine on kernel 2.2 > > 2. Evolution works fine on kernel 2.4 > > 3. Evolution does not work fine on kernel 2.5... > > > > Seems pretty obvious to me where the problem is - kernel 2.5, it is the > > only thing that has changed in the equation. > > > > well, unless kernels 2.2 and 2.4 were broken in such a way that made > > Evolution work :-) > > But assuming that was the case, then it could be argued that kernel 2.5 > > *is* broken for changing behavior. > > > That's a too simplistic proof for deciding where the problem lies. For > exemple, due to multi-threading and other concurrent paradigms, a > semaphore problem could have lied undetected in Evolution for a while > and the 2.5.x kernel could have revealed it without changing its > behavior. > > Given that the user experience a hang, that sounds possible. > > The risk that the problem lies in the 2.5.x kernel seems to be greater > anyway, but it's far from being certain. > > Jerome -- Jeffrey Stedfast Evolution Hacker - Ximian, Inc. [EMAIL PROTECTED] - www.ximian.com _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
