Hy.
On 03.05.11 15:45, Zoltan Varga wrote:
Q1: Besides the monitor enter/exit trampolines, there
are other trampoline types which might not end up
in a C-function (and use, for example, optimized code
instead)?
All trampolines are hand written assembly code, but most of
Hi,
Those trampolines are in tramp-ARCH.c, they are called
monitor_enter/exit_trampoline ().
Zoltan
On Fri, Apr 29, 2011 at 3:39 PM, Martin Daeumler m...@cs.tu-chemnitz.dewrote:
On March 10, 2010, Paolo Molaro wrote:
Further, I traced it down into the mono 2.6.1 code tree, and
Hi,
The fix caused some regressions and had to be reverted. So this issue is
still open.
Zoltan
On Sat, Mar 6, 2010 at 8:23 PM, Zoltan Varga var...@gmail.com wrote:
Hi,
This is now fixed in SVN HEAD/2.6 branch.
Zoltan
On Thu, Mar 4, 2010 at 3:12
Hi,
This is now fixed in SVN HEAD/2.6 branch.
Zoltan
On Thu, Mar 4, 2010 at 3:12 PM, cpMon page@gmail.com wrote:
I never get a signal when System.Threading.Monitor::Exit gets called too
many
times. Further, I traced it down into the mono 2.6.1 code tree, and
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:
I never get a signal when System.Threading.Monitor::Exit gets called too many
times. Further, I traced it down into the mono 2.6.1 code tree, and
mono_monitor_exit is never called. The trampoline generates the code, but
it's never called. Can you provide a quick fix? It seems like a glaring bug.
Please file a bug report so we can track this problem.
On Thu, Mar 4, 2010 at 11:12 AM, cpMon page@gmail.com wrote:
I never get a signal when System.Threading.Monitor::Exit gets called too
many
times. Further, I traced it down into the mono 2.6.1 code tree, and
mono_monitor_exit is
On 03/04/10 cpMon wrote:
I never get a signal when System.Threading.Monitor::Exit gets called too many
times.
We used to raise an exception, but IIRC, the MS runtime doesn't throw it
either, so we don't anymore.
Further, I traced it down into the mono 2.6.1 code tree, and
mono_monitor_exit
11 matches
Mail list logo
