[Mono-bugs] [Bug 80579][Cri] New - Segmentation fault when executing application

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Jan 22 11:45:29 EST 2007


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 rahorvat at yahoo.com.

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

--- shadow/80579	2007-01-22 11:45:29.000000000 -0500
+++ shadow/80579.tmp.15723	2007-01-22 11:45:29.000000000 -0500
@@ -0,0 +1,65 @@
+Bug#: 80579
+Product: Mono: Runtime
+Version: 1.2
+OS: Debian Woody
+OS Details: Kernel 2.4.27-3-686-smp, 768 MB, 2xIntel Pentium III
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Critical
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: rahorvat at yahoo.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Segmentation fault when executing application
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+Segmentation fault when executing application on Debian Linux. The same
+application executes correctly on Windows. The error appears when
+application has more data to process.
+I have to emphasize that I'm new to mono project (not .NET) and I have
+(possibly) missed some important description or something.
+
+Steps to reproduce the problem:
+1. 
+2. 
+3. 
+
+Actual Results: This is from gdb.
+Native stacktrace:
+
+        mono [0x815b8ed]
+        mono [0x81457b7]
+        /lib/libpthread.so.0 [0x400bc8cb]
+        /lib/libc.so.6 [0x4014d670]
+        mono(mono_domain_set_internal+0x40) [0x80e0ba0]
+        mono [0x80d520f]
+        mono [0x80d65a6]
+        mono [0x80d66ac]
+        mono [0x8094612]
+        mono [0x80fbe97]
+        mono [0x811ab95]
+        /lib/libpthread.so.0 [0x400b6e51]
+        /lib/libc.so.6(__clone+0x5a) [0x401fb8aa]
+
+Debug info from gdb:
+
+=================================================================
+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.
+=================================================================
+
+
+Expected Results:
+Application exits successfuly, eg. without Segmentation fault.
+
+How often does this happen? 
+When application is processing more data and allocating more memory.
+
+Additional Information:


More information about the mono-bugs mailing list