[Mono-bugs] [Bug 76843][Nor] Changed - Crash in monitor.c:203 (mono_monitor_try_enter_internal)

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Dec 5 12:25:42 EST 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 dick at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=76843

--- shadow/76843	2005-11-29 12:10:58.000000000 -0500
+++ shadow/76843.tmp.25832	2005-12-05 12:25:42.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 76843
 Product: Mono: Runtime
 Version: 1.1
 OS: unknown
 OS Details: SUSE 10.0
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: WONTFIX
 Severity: Unknown
 Priority: Normal
 Component: JIT
 AssignedTo: dick at ximian.com                            
 ReportedBy: abockover at novell.com               
 QAContact: mono-bugs at ximian.com
@@ -101,6 +101,18 @@
 
 dbus-0.50/mono/ProxyBuilder.cs: ProxyBuilder.BuildFinalizer
 
 
 ------- Additional Comments From gonzalo at ximian.com  2005-11-29 12:10 -------
 dbus-sharp 0.60 works fine for me on suse 10.
+
+------- Additional Comments From dick at ximian.com  2005-12-05 12:25 -------
+The crash is happening because the DbusObject.Proxy finalizer is
+passing the object vtable (instead of the object itself) to the
+Monitor lock.  Probably somewhere in that mess of hand-crafted IL.
+
+Closing as WONTFIX for now, because:
+
+a) dbus-0.60 fixes its bug; but
+b) we really ought to protect the runtime from bogus objects being
+passed to it, though I can't think of a suitably efficient way right now.
+


More information about the mono-bugs mailing list