[Mono-bugs] [Bug 52553][Nor] New - subclass Foo : Class2.Ibar leads to MCS exception

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

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

--- shadow/52553	2004-03-13 01:43:11.000000000 -0500
+++ shadow/52553.tmp.25484	2004-03-13 01:43:11.000000000 -0500
@@ -0,0 +1,64 @@
+Bug#: 52553
+Product: Mono: Compilers
+Version: unspecified
+OS: unknown
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Normal
+Component: C#
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: sebastian@nowozin.de               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: subclass Foo : Class2.Ibar leads to MCS exception
+
+Description of Problem:
+
+Upon compiling the attached example program MCS exits with an internal
+unhandled NullReferenceException in Mono.CSharp.Interface:DefineType ().
+
+Steps to reproduce the problem:
+1. Unpack the attached example program
+2. run ./build.sh
+
+Actual Results:
+
+Unhandled Exception: System.NullReferenceException: A null value was found
+where an object instance was required
+in <0x0020c> Mono.CSharp.Interface:DefineType ()
+in <0x001ec> Mono.CSharp.DeclSpace:LookupInterfaceOrClass (string,string,bool&)
+in <0x00140> Mono.CSharp.DeclSpace:FindType (Mono.CSharp.Location,string)
+...
+(complete calltree)
+
+
+Expected Results:
+
+Either successful compilation (I expect the program to be valid), or a
+meaningful bug message.
+
+
+How often does this happen? 
+
+Everytime.
+
+
+Additional Information:
+
+Mono C# compiler version 0.28.42650.0, manually build on an up-to-date
+Debian/sid.
+
+------- Additional Comments From sebastian@nowozin.de  2003-12-25 01:10 -------
+Created an attachment (id=6325)
+Two minimal .cs files and a build.sh that reproduce this bug.
+
+
+------- Additional Comments From miguel@ximian.com  2004-03-13 01:43 -------
+Will look into this bug;
+
+For now, if you change the compilation order, you will get it to run
+(just swap the two filenames).