[Mono-bugs] [Bug 59570][Wis] New - Consistent application hang/segfaults with mono-0.95

[bugzilla-daemon@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 latexer@gentoo.org.

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

--- shadow/59570	2004-06-03 14:32:30.000000000 -0400
+++ shadow/59570.tmp.14144	2004-06-03 14:32:30.000000000 -0400
@@ -0,0 +1,69 @@
+Bug#: 59570
+Product: Mono: Runtime
+Version: unspecified
+OS: 
+OS Details: Gentoo (with NPTL glibc)
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: latexer@gentoo.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Consistent application hang/segfaults with mono-0.95
+
+Starting at some point with the new beta2, both muine and blam started
+behaving erratically. Currently gdb doesn't seem to do anything useful for
+me, but running mono --trace on both shows the following:
+
+muine:
+ . . . . . . . ENTER: System.IO.FileStream:InitBuffer
+(int,bool)(this:0x8ae9a50[System.IO.FileStream muine.exe], 8192, 0, )
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. . . . . . . . . . . ENTER: (wrapper managed-to-native)
+System.Object:__icall_wrapper_mono_array_new_specific
+(intptr,int)(0x8358d98, 8192, )
+Segmentation fault
+
+
+blam: . . . . . . . . . . . . . . . . . . . . . . . . . . . LEAVE:
+System.Console:WriteLine (string,object)
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTER: (wrapper
+managed-to-native) System.Object:__icall_wrapper_mono_array_new_specific
+(intptr,int)(0x8437e58, 114688, )
+
+Blam simply hangs (this always happens at the exact same spot on one blog
+post) and muine segfaults. From the description in the comments in the
+mono_array_new_specific, it sounds like there's some issues with allocating
+the wrong memory when trying to create the new arrays.
+
+System is a pentium4, reproducable with -march=pentium4, or with no CFLAGS
+what-so-ever. I've tried latest mono and gtk-sharp HEAD, and the problem
+still remains.
+
+I'd get a backtrace, but all the suggestions i've gotten still leave me with:
+
+peter@gonzo blam $ gdb /usr/bin/mono
+GNU gdb 6.1
+Copyright 2004 Free Software Foundation, Inc.
+GDB is free software, covered by the GNU General Public License, and you are
+welcome to change it and/or distribute copies of it under certain conditions.
+Type "show copying" to see the conditions.
+There is absolutely no warranty for GDB.  Type "show warranty" for details.
+This GDB was configured as "i486-pc-linux-gnu"...(no debugging symbols
+found)...Using host libthread_db library "/lib/libthread_db.so.1".
+
+(gdb) r blam.exe
+Starting program: /usr/bin/mono blam.exe
+(no debugging symbols found)...(no debugging symbols found)...(no debugging
+symbols found)...(no debugging symbols found)...Detaching after fork from
+child process 18906.
+
+Program terminated with signal SIGTRAP, Trace/breakpoint trap.
+The program no longer exists.
+(gdb)