[Mono-bugs] [Bug 49824][Nor] Changed - Threading.SyncronizationException thrown on calling Monitor.Exit on an object that has not been locked.

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Jun 24 03:50:45 EDT 2005

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by gonzalo at ximian.com.


--- shadow/49824	2005-06-24 01:52:14.000000000 -0400
+++ shadow/49824.tmp.22704	2005-06-24 03:50:45.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 49824
 Product: Mono: Runtime
 Version: unspecified
 OS: Red Hat 9.0
 OS Details: Standard Install
-Status: NEW   
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: bmaurer at users.sf.net                            
 ReportedBy: gileslforster at yahoo.co.uk               
 QAContact: mono-bugs at ximian.com
@@ -128,6 +128,9 @@
 specified object" could be read so as to not throw
 SynchronizationLockException when the object is not locked at all, but
 unless my test above is faulty, it isn't thrown even when another
 thread _does_ own the lock.  (Changing the Monitor.Exit(x) into a
 Monitor.Enter(x) does deadlock as expected though.)
+------- Additional Comments From gonzalo at ximian.com  2005-06-24 03:50 -------
+This was fixed on 2005-05-05.

More information about the mono-bugs mailing list