Hi,
Applied to SVN HEAD/2.6 branch.
thanks
Zoltan
On Thu, Mar 4, 2010 at 12:14 PM, David Miller da...@davemloft.net wrote:
This was the minimal set of changes I needed to get mainline
to build for me.
libgc/
2010-03-04 David S. Miller da...@davemloft.net
According to the 2.0 .net MS spec, an exception is thrown for
System.Threading.Monitor . From them:
Exceptions
Exception type Condition
ArgumentNullException
The obj parameter is a null reference (Nothing in Visual Basic).
SynchronizationLockException
The current thread
Hi,
The documentation says this, but the MS implementation works otherwise.
Zoltan
On Fri, Mar 5, 2010 at 4:02 PM, cpMon page@gmail.com wrote:
According to the 2.0 .net MS spec, an exception is thrown for
System.Threading.Monitor . From them:
Exceptions
On 05.03.2010 16:09, Zoltan Varga wrote:
Hi,
The documentation says this, but the MS implementation works otherwise.
MS started throwing with 2.0. It didn't throw before, though.
using System;
using System.Threading;
class Test
{
static object locker = new object ();
My Visual Studio 2005 throws the exception.
Specifically, what version of the .net frawmwork do you support? If it 1.1,
then I can see your point, but 2.0 and beyond, the mono code should do the
exception.
Cal Page
--
View this message in context:
The shared memory files are created in /dev/shm/... on linux, but the code
tries to find them in your home account. Since the file doesn't exist, a 0
is returned from ftok. This results in a pileup of shm's and semaphores. Run
ipcs -a after every run to see the probmem.
Cal Page
Here's the
Hi,
Applied to to SVN HEAD/2.6/2.4 branches.
Zoltan
On Fri, Mar 5, 2010 at 6:21 PM, cpMon page@gmail.com wrote:
The shared memory files are created in /dev/shm/... on linux, but the code
tries to find them in your home account. Since the file doesn't exist, a 0
is
