[Mono-bugs] [Bug 72522][Wis] New - mono --aot'ed code throws some unexpected NullReferenceException

[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 nazgul@omega.pl.

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

--- shadow/72522	2005-02-11 18:58:42.000000000 -0500
+++ shadow/72522.tmp.7124	2005-02-11 18:58:42.000000000 -0500
@@ -0,0 +1,57 @@
+Bug#: 72522
+Product: Mono: Runtime
+Version: 1.0
+OS: 
+OS Details: Mandrake Linux 10.1  mono svn from 11.02.2005
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: nazgul@omega.pl               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mono --aot'ed code throws some unexpected NullReferenceException
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+Some NullReferenceException is being thrown by runtime when Nemerle
+compiler try to compile code with large numbers. 
+Note that exception is not catchable, because ncc catched all exceptions in 
+its main loop.
+
+Steps to reproduce the problem:
+1. Download ncc.exe and *.dll from http://nemerle.org/svn/nemerle/trunk/boot/
+2. mono --aot Nemerle.Compiler.dll
+3. cat > t.n
+module M {
+  Main () : void { 
+     _ = 444444444444444;
+  }
+}
+
+4. mono ncc.exe t.n
+
+Actual Results:
+Unhandled Exception: System.NullReferenceException: Object reference not
+set to an instance of an object
+
+
+Expected Results:
+after rm Nemerle.Compiler.dll.so it is:
+t.n:48:25: error: number literal 444444444444444 is too large for given type
+
+How often does this happen? 
+with this particular scenario always. all other programs compiles fine with 
+aoted code
+
+Additional Information:
+you can also do svn co http://nemerle.org/svn/nemerle/trunk/boot/ 
+to download assemblies
+
+Sorry for complex reproduce scenario, if needed I will try to separate this 
+issue.