[Mono-bugs] [Bug 75042][Nor] New - Runtime see nonnull value in notinitialized struct field

[bugzilla-daemon at 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 nazgul at omega.pl.

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

--- shadow/75042	2005-05-25 10:28:46.000000000 -0400
+++ shadow/75042.tmp.26573	2005-05-25 10:28:46.000000000 -0400
@@ -0,0 +1,71 @@
+Bug#: 75042
+Product: Mono: Runtime
+Version: 1.0
+OS: 
+OS Details: mono svn from 24 May 2005
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: JIT
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: nazgul at omega.pl               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Runtime see nonnull value in notinitialized struct field
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+The attached program (out.exe) comes from following Nemerle source code
+(just for reference).
+
+public class thistest
+{
+    struct xxx
+    {
+        public this()
+        {
+        }
+        public a: list [int];
+    };
+    static Main(): void
+    {
+        def x = xxx();
+        assert (x.a == null);
+      
+        match(x.a)
+        {
+            | _ :: _ => System.Console.WriteLine("?");
+            | [] => System.Console.WriteLine("!");
+        }        
+    }
+};
+
+Removing the match expression seem to change the runtime behaviour of
+assert comparison (out1.exe)
+
+
+Steps to reproduce the problem:
+1. Unpack files from test.zip
+2. mono out.exe
+
+
+Actual Results:
+Unhandled Exception: Nemerle.Core.AssertionException: assertion ``x.a ==
+null'' failed in file t.n, line 14
+in <0x00066> thistest:Main ()
+
+
+Expected Results:
+Unhandled Exception: Nemerle.Core.NullMatchException: 
+
+
+How often does this happen? 
+Always
+
+Additional Information:
+I'm marking it as JIT bug, because the presence of code after the assert
+influences the results.