Bugzilla – Bug 315575
assertion failure: debugger_lock_level > 0
Last modified: 2007-09-15 21:24:46 UTC
---- Reported by michi@zeroc.com 2004-07-23 02:40:50 MST ---- I just got the following assertion failure when running a program with --debug: ** ERROR **: file mono-debug-debugger.c: line 92 (mono_debugger_unlock): assertion failed: (debugger_lock_level > 0) aborting... It appears to be a race condition. I can reproduce this on a dual-CPU RH8 machine, but only once in maybe 25-50 runs or so. Cheers, Michi. ---- Additional Comments From bmaurer@users.sf.net 2004-07-23 16:21:50 MST ---- Hello, Duncan ran mcs under --debug on our dual proc box. We could not get it to fail. Can you give us a program which fails for you? Also, does booting in single proc mode fix things? ---- Additional Comments From bmaurer@users.sf.net 2004-11-05 23:45:07 MST ---- 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:33 MST ---- 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. ---- Additional Comments From vargaz@gmail.com 2005-05-06 10:05:37 MST ---- *** This bug has been marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=MONO74830 *** Unknown bug field "cf_op_sys_details" encountered while moving bug <cf_op_sys_details>RedHat 8</cf_op_sys_details> Unknown operating system unknown. Setting to default OS "Other". This bug was marked DUPLICATE in the database it was moved from. Changing resolution to "MOVED"