[Mono-bugs] [Bug 78315][Nor] Changed - Crash in 3 line System.Windows.Forms program

[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 sebastien at ximian.com.

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

--- shadow/78315	2006-05-06 15:10:09.000000000 -0400
+++ shadow/78315.tmp.13534	2006-07-05 15:56:18.000000000 -0400
@@ -10,13 +10,12 @@
 Component: Windows.Forms
 AssignedTo: peter at novonyx.com                            
 ReportedBy: bbjamey at gmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
-Cc: 
 Summary: Crash in 3 line System.Windows.Forms program
 
 Please fill in this template when reporting a bug, unless you know what 
 you are doing.
 Description of Problem: Crash in 3 line System.Windows.Forms program
 
@@ -107,6 +106,84 @@
 ------- Additional Comments From bbjamey at gmail.com  2006-05-06 15:10 -------
 Yes, Windows - thanks.  I searched for "GdipDisposeImage" in the bug 
 database before submitting but didn't get anything. 
 
 
 bj
+
+------- Additional Comments From sebastien at ximian.com  2006-07-05 15:56 -------
+It looks like this can happen too on Linux, only a little harder to
+reproduce.
+
+Tracing exception indicates we have a NRE near the end of the execution.
+
+> mono --trace=T:X 78315.exe
+
+poupou at poupou:~/src/bugzilla> mono --trace=T:X 78315.exe
+EXCEPTION handling: FileNotFoundException
+Mono System.Windows.Forms Assembly [$auto_build_revision$]
+Gtk colorscheme read
+x1 = System.Windows.Forms.Form, Text:
+EXCEPTION handling: NotSupportedException
+... lots of EXCEPTION handling: NotSupportedException ...
+EXCEPTION handling: NotSupportedException
+EXCEPTION handling: NullReferenceException
+
+
+A full log aborts with a SIGSEGV, but still show where the problem is.
+
+> mono --trace 78315.exe > 78315.log
+
+=================================================================
+Got a SIGSEGV while executing native code. This usually indicates
+a fatal error in the mono runtime or one of the native libraries
+used by your application.
+=================================================================
+
+Stacktrace:
+
+
+Native stacktrace:
+
+        mono(mono_handle_native_sigsegv+0xac) [0x814ef0c]
+        mono [0x811dcec]
+        [0xffffe440]
+        [0x4187e730]
+        [0x4187e6a2]
+        mono(mono_runtime_delegate_invoke+0x2a) [0x80d0d4a]
+        mono(mono_runtime_run_main+0x238) [0x80d5538]
+        mono(mono_main+0x1024) [0x805e654]
+        /lib/tls/libc.so.6(__libc_start_main+0xd0) [0x4012eea0]
+        mono [0x805d0e1]
+Aborted
+
+Tail of the log file...
+
+. . . . . . . . . . . . . LEAVE:
+System.IO.UnexceptionalStreamWriter:Write (char[])
+. . . . . . . . . . . . LEAVE: System.IO.TextWriter:WriteLine ()
+. . . . . . . . . . . LEAVE: System.IO.TextWriter:WriteLine
+(string,object)
+. . . . . . . . . . . ENTER: System.Threading.Monitor:Exit
+(object)([System.IO.SynchronizedWriter:0x56c20], )
+. . . . . . . . . . . . ENTER: (wrapper managed-to-native)
+System.Threading.Monitor:Monitor_exit
+(object)([System.IO.SynchronizedWriter:0x56c20], )
+. . . . . . . . . . . . LEAVE: (wrapper managed-to-native)
+System.Threading.Monitor:Monitor_exit (object)
+. . . . . . . . . . . LEAVE: System.Threading.Monitor:Exit (object)
+. . . . . . . . . . LEAVE: System.IO.SynchronizedWriter:WriteLine
+(string,object)
+. . . . . . . . . LEAVE: System.Console:WriteLine (string,object)
+. . . . . . . . LEAVE: C:Main ()
+. . . . . . . LEAVE: (wrapper runtime-invoke)
+System.Object:runtime_invoke_void
+(object,intptr,intptr,intptr)[OBJECT:(nil)]
+. . . . . . . ENTER: (wrapper runtime-invoke)
+System.Object:runtime_invoke_void_object_EventArgs
+(object,intptr,intptr,intptr)([System.EventHandler:0x4a690],
+0xbfe58340, 0xbfe58348, 0x41caf720, )
+. . . . . . . . ENTER: (wrapper delegate-invoke)
+System.MulticastDelegate:invoke_void_object_EventArgs
+(object,System.EventArgs)(this:0x4a690[System.EventHandler 78315.exe], 
+
+so we're still processing events after Main has ended.