[Mono-bugs] [Bug 75664][Cri] Changed - debugger mutex not init'd early enough

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Jul 29 15:17:58 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 martin at ximian.com.


--- shadow/75664	2005-07-29 13:05:01.000000000 -0400
+++ shadow/75664.tmp.3610	2005-07-29 15:17:58.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 75664
 Product: Mono: Runtime
 Version: 1.1
 OS: other
 OS Details: NetBSD 3.0
-Status: NEW   
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Critical
 Component: debug
 AssignedTo: martin at ximian.com                            
 ReportedBy: jlaban at wanadoo.Fr               
 QAContact: mono-bugs at ximian.com
@@ -38,6 +38,14 @@
 default. A mutex normally held by a critical_section is used but not 
 ------- Additional Comments From bmaurer at users.sf.net  2005-07-29 13:05 -------
 Luckily, on Linux, things work fine here, i guess 0 init'd stuff works
 fine. However we should fix this. Martin, where does this need to happen?
+------- Additional Comments From martin at ximian.com  2005-07-29 15:17 -------
+Fixed in SVN.
+As a general rule, nobody outside mono-debug.c (and
+debug-mono-symfile.c) is allowed to call mono_debugger_lock/unlock().
+ These functions must check whether we actually have debugging support
+or not.

More information about the mono-bugs mailing list