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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=75664 --- 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 -Resolution: +Status: RESOLVED +Resolution: FIXED Severity: Unknown Priority: Critical Component: debug AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] @@ -38,6 +38,14 @@ default. A mutex normally held by a critical_section is used but not initialized. ------- Additional Comments From [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
