[Mono-bugs] [Bug 48591][Wis] New - Non-deterministic failure of --debug

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 16 Sep 2004 17:37:55 -0400 (EDT)

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 gonzalo@ximian.com.


--- shadow/48591	2004-09-16 17:37:55.000000000 -0400
+++ shadow/48591.tmp.14811	2004-09-16 17:37:55.000000000 -0400
@@ -0,0 +1,46 @@
+Bug#: 48591
+Product: Mono: Runtime
+Version: unspecified
+OS: unknown
+OS Details: 
+Status: ASSIGNED   
+Severity: Unknown
+Priority: Wishlist
+Component: misc
+AssignedTo: martin@ximian.com                            
+ReportedBy: bmaurer@users.sf.net               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: Non-deterministic failure of --debug
+Description of Problem:
+When running tests from the Xalan XSLT test suite using --debug for mono, I
+randomly get errors like:
+** ERROR **: file mono-debug.c: line 274 (mono_debug_add_method): assertion
+failed: (!domain_data->jit [minfo->index])
+./run-suite-dir.sh: line 25: 23119 Aborted                 ( mono --debug
+xslt.exe $NAME.xsl $NAME.xml )
+The error does not show up on a specific file, only randomly, about 1/100th
+of the time.
+Sadly, I can't get any more info ;-(.
+------- Additional Comments From martin@ximian.com  2003-10-11 12:34 -------
+There's now a workaround in CVS; this bug has a very low priority 
+for me because of the nature of this bug: 
+Sometimes (with a probability of < 1%), one random method doesn't 
+get any debugging information.  This means that if some application 
+ever throws an exception or crashes in this method, you won't get 
+any line numbers.  It is highly unlikely that this will ever happen 
+and if it ever happens, you can most likely re-run the application 
+100 times before you get it the second time - and then it'll most 
+likely affect another method. 
+------- Additional Comments From gonzalo@ximian.com  2004-09-16 17:37 -------
+this might have been fixed by the locks added to the debugging code.