[Mono-bugs] [Bug 75132][Maj] New - segfault when running a .NET 2.0 compiled binary

[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 matt.hargett at logiclibrary.com.

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

--- shadow/75132	2005-06-02 21:09:38.000000000 -0400
+++ shadow/75132.tmp.17266	2005-06-02 21:09:38.000000000 -0400
@@ -0,0 +1,66 @@
+Bug#: 75132
+Product: Mono: Runtime
+Version: 1.1
+OS: SLES 9
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: interop
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: matt.hargett at logiclibrary.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: segfault when running a .NET 2.0 compiled binary
+
+Description of Problem:
+We usually compile and run our product using mono, but compiling in VS2005
+beta 2 and running under mono causes mono to segfault. We aren't using
+generics or any C# 2.0 features -- this all compiles and runs just fine in
+VS2003 as well.
+
+
+Steps to reproduce the problem:
+1. using mono svn head
+mono ./BugScan.exe
+
+Actual Results:
+** (BugScan.exe:18073): WARNING **: Missing method Sort in assembly
+/home/matt/bs-net2/Common.dll, type Array
+
+** (BugScan.exe:18073): WARNING **: Missing method Sort in assembly
+/home/matt/bs-net2/Common.dll, type Array
+Segmentation fault
+
+gdb reports the segfault as:
+Program received signal SIGSEGV, Segmentation fault.
+[Switching to Thread 182906882336 (LWP 18063)]
+0x000000000048f96f in mono_get_method_from_token (image=0x777bf0,
+token=721420289, klass=0x0, context=0x0) at loader.c:480
+480             if (method->is_inflated)
+(gdb) c
+Continuing.
+
+Program received signal SIGSEGV, Segmentation fault.
+0x00000000004ea4ff in mono_arch_find_jit_info (domain=0x6e5eb0,
+jit_tls=<value optimized out>, res=0x7fbfffe7c0, prev_ji=0x10,
+    ctx=0x7fbfffe890, new_ctx=0x7fbfffe6e0, trace=0x0, lmf=0x7fbfffe6d0,
+native_offset=0x0, managed=0x7fbfffe634)
+    at exceptions-amd64.c:515
+515                     if (*lmf && (MONO_CONTEXT_GET_BP (ctx) >=
+(gpointer)(*lmf)->ebp)) {
+
+
+Expected Results:
+Definitely shouldn't segfault. It should hopefully run just fine, just like
+the mcs compiled binary does and like it does under MS.NET 2.0 beta 2. 
+
+
+How often does this happen? 
+Every time.
+
+Additional Information:
+Debugging mono with SLES9's gdb is strange, so this gdb output might be wrong.