Hi Crista, Hi Homer, That would make much sense to me. I run regions on Windows and on SuSe Linux 11.1 64bit (wich comes with MONO 2.0.1) I read about all the trouble with tp - but never have a realy bad time the last while...
But in total I agree on Linux/MONO bringing more strange results (even from RL experience) than on Win/.Net platform. Cheers Ralf Date: Wed, 14 Jan 2009 07:57:03 +0100 From: "Homer Horwitz" <[email protected]> Subject: Re: [Opensim-dev] .NET / Mono lock(obj) statement To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8 Hi Diva, On Wed, Jan 14, 2009 at 5:57 AM, Diva Canto <[email protected]> wrote: > Here's a simplified version of the problem: > > lock (a) > { > foo(); > } > > void foo() > { > lock (a) > { > ... > } > } I just tried that with Mono 2.0.1, and it works correctly (i.e. it doesn't deadlock). I used an instance variable object a = new object() for the lock. > (the real situation is a bit more complicated; foo() involves a > delegate; but ignore that) Is this maybe necessary to get the (wrong) result? Or did you use another Mono version? Cheers, Homer _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
