[Mono-bugs] [Bug 61867][Maj] Changed - assertion failure: debugger_lock_level > 0

[bugzilla-daemon@bugzilla.ximian.com]

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 michi@zeroc.com.

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

--- shadow/61867	2004-11-05 23:45:07.000000000 -0500
+++ shadow/61867.tmp.2594	2005-05-06 02:20:34.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 61867
 Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: RedHat 8
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Major
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: michi@zeroc.com               
 QAContact: mono-bugs@ximian.com
@@ -38,6 +38,19 @@
 Also, does booting in single proc mode fix things?
 
 ------- Additional Comments From bmaurer@users.sf.net  2004-11-05 23:45 -------
 We fixed alot of --debug races a while ago when trying to fix mod_mono
 stability problems. So it is probably fixed. If this pops up again,
 please re-open.
+
+------- Additional Comments From michi@zeroc.com  2005-05-06 02:20 -------
+I'm sorry, but I just got that again, using Mono 1.1.7:
+
+** ERROR **: file mono-debug-debugger.c: line 83
+(mono_debugger_unlock): assertion failed: (debugger_lock_level > 0)
+aborting...
+
+It's a race -- I get this only rarely. Just did another 200 runs or so
+without it showing up again. This is still in dual-CPU mode. I'll let
+this run for a while and see whether I can get it a second time. and
+I'll try and run the tests over the weekend in single-CPU mode, to see
+whether the failure shows up then.