[Mono-bugs] [Bug 79194][Nor] New - NullReferenceException crashes embedded Mono

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Aug 28 10:17:32 EDT 2006

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 janne.rantala at gmail.com.


--- shadow/79194	2006-08-28 10:17:32.000000000 -0400
+++ shadow/79194.tmp.10463	2006-08-28 10:17:32.000000000 -0400
@@ -0,0 +1,68 @@
+Bug#: 79194
+Product: Mono: Runtime
+Version: unspecified
+OS: Windows XP
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: interop
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: janne.rantala at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: NullReferenceException crashes embedded Mono
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+When method in managed code is invoked from embedded Mono, if
+NullReferenceException which is not handled, occurs in managed world, Mono
+crashes. Normally unhandled exceptions can be stored in MonoObject, but
+this time error message "0xC0000005: Access violation reading location
+0x00000000" appears. Method in managed code is invoked with
+Steps to reproduce the problem:
+1. Here's the sample code in C#
+using System;
+using System.Collections.Generic;
+using System.Text;
+namespace CrashTest
+    public class Class1
+    {
+        public void CrashMe()
+        {
+            try
+            {
+                throw new Exception("test");
+            }
+            catch (Exception e)
+            {
+                Console.WriteLine(e.InnerException.Message);
+            }
+        }
+    }
+2. Invoke method CrashMe from embedded environment with mono_runtime_invoke. 
+Actual Results:
+"0xC0000005: Access violation reading location 0x00000000"
+Expected Results:
+Unhandled exception is supposed to be stored in MonoObject.
+How often does this happen? 
+Every time.
+Additional Information:
+This only happens in embedded Mono and Windows. If same program is ran from
+command line, it works ok. As well as embedded Mono in Linux.

More information about the mono-bugs mailing list