[Mono-bugs] [Bug 80580][Maj] New - LayoutKind.Sequential attribute is not respected on a class

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

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

--- shadow/80580	2007-01-22 11:59:54.000000000 -0500
+++ shadow/80580.tmp.15902	2007-01-22 11:59:54.000000000 -0500
@@ -0,0 +1,106 @@
+Bug#: 80580
+Product: Mono: Runtime
+Version: 1.2
+OS: GNU/Linux [Other]
+OS Details: Gentoo 2.6.19
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: interop
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: ximian.bugzilla at analogcoast.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: LayoutKind.Sequential attribute is not respected on a class
+
+Mono runtime crashes with following error message when running attached
+source. Source runs properly on .NET 2.0 on windows.
+
+Steps to reproduce the problem
+------------------------------
+1. Compile attached source (ClassStructBug.cs). 
+2. mono ClassStructBug.exe
+3. get a runtime error
+
+
+Actual Results
+--------------
+** ERROR **: file object.c: line 602 (compute_class_bitmap): assertion
+failed: ((field->offset % sizeof(gpointer)) == 0)
+aborting...
+Stacktrace:
+
+Native stacktrace:
+
+        mono [0x8159694]
+        [0xb7f85440]
+        /lib/libc.so.6(abort+0xec) [0xb7d75bdc]
+        /usr/lib/libglib-2.0.so.0 [0xb7ef047b]
+
+Debug info from gdb:
+
+(no debugging symbols found)
+Using host libthread_db library "/lib/libthread_db.so.1".
+(no debugging symbols found)
+(no debugging symbols found)
+(no debugging symbols found)
+(no debugging symbols found)
+(no debugging symbols found)
+[Thread debugging using libthread_db enabled]
+[New Thread -1210799888 (LWP 29210)]
+[New Thread -1219052656 (LWP 29212)]
+[New Thread -1208632432 (LWP 29211)]
+0xb7f85410 in ?? ()
+  3 Thread -1208632432 (LWP 29211)  0xb7f85410 in ?? ()
+  2 Thread -1219052656 (LWP 29212)  0xb7f85410 in ?? ()
+  1 Thread -1210799888 (LWP 29210)  0xb7f85410 in ?? ()
+
+Thread 3 (Thread -1208632432 (LWP 29211)):
+#0  0xb7f85410 in ?? ()
+#1  0xb7f5b388 in ?? ()
+#2  0x081f0a80 in ?? ()
+#3  0x00000000 in ?? ()
+
+Thread 2 (Thread -1219052656 (LWP 29212)):
+#0  0xb7f85410 in ?? ()
+#1  0xb756b188 in ?? ()
+#2  0x00000001 in ?? ()
+#3  0x00000000 in ?? ()
+
+Thread 1 (Thread -1210799888 (LWP 29210)):
+#0  0xb7f85410 in ?? ()
+#1  0xbfa655bc in ?? ()
+#2  0x00000000 in ?? ()
+#0  0xb7f85410 in ?? ()
+
+
+=================================================================
+Got a SIGABRT while executing native code. This usually indicates
+a fatal error in the mono runtime or one of the native libraries
+used by your application.
+=================================================================
+
+Expected Results
+----------------
+1 2 3
+1 2 3
+
+How often does this happen? Every time
+
+Additional Information
+----------------------
+> mono --version
+Mono JIT compiler version 1.2.20070113, (C) 2002-2006 Novell, Inc and
+Contributors. www.mono-project.com
+        TLS:           __thread
+        GC:            Included Boehm (with typed GC)
+        SIGSEGV:       normal
+        Architecture:  x86
+        Disabled:      none
+
+This bug has also been reproduced with 1.2.2.1 runtime. 
+
+.exe compiled on Mono works fine on Windows producing expected results.