[Mono-bugs] [Bug 78227][Nor] New - erroneous error with Monitor.Pulse

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Apr 27 20:06:58 EDT 2006

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 james at ximian.com.


--- shadow/78227	2006-04-27 20:06:58.000000000 -0400
+++ shadow/78227.tmp.2097	2006-04-27 20:06:58.000000000 -0400
@@ -0,0 +1,46 @@
+Bug#: 78227
+Product: Mono: Runtime
+Version: 1.1
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: james at ximian.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: erroneous error with Monitor.Pulse
+Unhandled Exception: System.Threading.SynchronizationLockException: Not
+locked by this thread
+in <0x00000> <unknown method>
+in (wrapper managed-to-native) System.Threading.Monitor:Monitor_pulse (object)
+in <0x0002d> System.Threading.Monitor:Pulse (System.Object obj)
+in <0x002ff> Novell.Zenworks.Zmd.Progress:OnStopped ()
+in (wrapper remoting-invoke-with-check)
+Novell.Zenworks.Zmd.Progress:OnStopped ()
+in <0x000b3> Novell.Zenworks.Zmd.Progress:Stop (ProgressStatus status,
+System.String me ssage)
+in <0x0004a> Novell.Zenworks.Zmd.MultiProgress:Stop (ProgressStatus status,
+System.Stri ng message)
+in <0x0002e> Novell.Zenworks.Zmd.Progress:Finish ()
+in (wrapper remoting-invoke-with-check) Novell.Zenworks.Zmd.Progress:Finish ()
+in <0x0005f> Novell.Zenworks.Zmd.MultiProgress:Start ()
+in (wrapper remoting-invoke-with-check)
+Novell.Zenworks.Zmd.MultiProgress:Start ()
+in <0x00470> Novell.Zenworks.Zmd.ServiceManager:LoadExistingServices ()
+in <0x00008> Novell.Zenworks.Zmd.ServiceManager:MountExisting ()
+in <0x006f4> Novell.Zenworks.Zmd.Daemon:Run (System.String[] args)
+in <0x00014> Novell.Zenworks.Zmd.ZmdStart:Main (System.String[] args)
+The code that was being executed was:
+lock (this) {
+    Monitor.Pulse (this);
+So there is no way it couldn't be locked.

More information about the mono-bugs mailing list