[Mono-bugs] [Bug 74611][Maj] New - ** ERROR **: file class.c: line 1972

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 14 Apr 2005 22:23:45 -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 krzys@cs.cornell.edu.

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

--- shadow/74611	2005-04-14 22:23:45.000000000 -0400
+++ shadow/74611.tmp.10150	2005-04-14 22:23:45.000000000 -0400
@@ -0,0 +1,52 @@
+Bug#: 74611
+Product: Mono: Compilers
+Version: 1.1
+OS: Windows XP
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Major
+Component: C#
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: krzys@cs.cornell.edu               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Summary: ** ERROR **: file class.c: line 1972
+
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+
+Compiler crashes, see below for details.
+
+Steps to reproduce the problem:
+
+Attempt to compile my project. Sorry, but I can't share my sources. I rely 
+on generics heavily, if that is of any help. You do have problems handling 
+generics, see my other report 73753. These issues may be related, although 
+I got rid of the code that revealed the other bug.
+
+Actual Results:
+
+Error popup window -> ** ERROR **: file class.c: line 1972 
+(mono_class_setup_parent): should not be reached aborting...
+
+Compilation output -> This application has requested the Runtime to 
+terminate it in an unusual way. Please contact the application's support 
+team for more information.
+
+Expected Results:
+
+Well, successful compilation.
+
+How often does this happen? 
+
+Always, and in all versions of Mono including the latest.
+
+Additional Information:
+
+If you could generate more insightful error messages, I could try to find 
+the very part of my stuff that causes this error, but I've got almost 800 
+source files, trying one by one to see where it crashes is not an option.