[Mono-bugs] [Bug 55934][Nor] New - Mono stack becoming corrupted

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 22 Mar 2004 21:12:05 -0500 (EST)

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 david.mitchell@telogis.com.


--- shadow/55934	2004-03-22 21:12:05.000000000 -0500
+++ shadow/55934.tmp.8349	2004-03-22 21:12:05.000000000 -0500
@@ -0,0 +1,39 @@
+Bug#: 55934
+Product: Mono: Runtime
+Version: unspecified
+OS Details: Redhat 9.0
+Status: NEW   
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: david.mitchell@telogis.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: Mono stack becoming corrupted
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+The stack of the mono runtime can become corrupted, causing requests for
+large blocks of memory, which normally result in a segfault.
+Steps to reproduce the problem:
+1. Compile the attached program (mcs -r:System.Drawing stack_corrupt.cs)
+2. Run it as normal
+3. When the program hangs, attach gdb to the mono process, look at the
+backtrace for each of the threads, the second thread shows the failed
+GC_malloc call and segfault
+Actual Results:
+Program hangs
+Expected Results:
+Program loads image and exits normally
+How often does this happen?