[Mono-bugs] [Bug 75755][Nor] New - NullRef exception in a try-filter block

[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 jankit at novell.com.

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

--- shadow/75755	2005-08-09 00:49:47.000000000 -0400
+++ shadow/75755.tmp.7018	2005-08-09 00:49:47.000000000 -0400
@@ -0,0 +1,65 @@
+Bug#: 75755
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: JIT
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: jankit at novell.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: NullRef exception in a try-filter block
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+
+Attached is 
+ 1. .vb file 
+ 2. the corresponding .exe compiled with vbc.exe. 
+ 3. slightly altered .il file to (try) narrow down the error
+
+It runs fine on ms.net but on mono it gives a NRE.
+
+Unhandled Exception: System.NullReferenceException: Object reference not
+set to an instance of an object
+in <0x00049> Module1:Main ()
+
+The filter block here starts like
+
+        filter {
+          IL_000d:  isinst [mscorlib]System.Exception
+
+But if i add a 
+          ldstr "#2"
+          call void class [mscorlib]System.Console::WriteLine (string)
+
+before the isinst, then it goes fine but this time it seems to execute the
+filter block twice! I've edited the original .il a bit to show this.
+
+The 2nd .il when run(ilasm'ed) shows:
+
+#1
+#2
+#2
+#4
+
+Whereas ms.net shows:
+
+#1
+#2
+#4
+
+With the filterblock starting directly with isinst, mono gives:
+
+#1
+
+Unhandled Exception: System.NullReferenceException: Object reference not
+set to an instance of an object
+in <0x00052> Module1:Main ()