[Mono-bugs] [Bug 78211][Maj] New - SIGSEGV on early Thread.Abort

[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 pawel.sakowski at mind-breeze.com.

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

--- shadow/78211	2006-04-26 10:34:53.000000000 -0400
+++ shadow/78211.tmp.12236	2006-04-26 10:34:53.000000000 -0400
@@ -0,0 +1,75 @@
+Bug#: 78211
+Product: Mono: Runtime
+Version: 1.1
+OS: GNU/Linux [Other]
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: pawel.sakowski at mind-breeze.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: SIGSEGV on early Thread.Abort
+
+Description of Problem:
+If a thread is aborted immediately after it's started, the runtime crashes
+on a SIGSEGV.
+
+Steps to reproduce the problem:
+using System.Threading;
+class Test {
+	static void Main() {
+		Thread t = new Thread(Callback);
+		t.Start();
+		//Thread.Sleep(100);
+		t.Abort();
+	}
+	static void Callback(object o) {}
+}
+
+Actual Results:
+(gdb) bt
+#0  0x00a197a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+#1  0x00a597d5 in raise () from /lib/tls/libc.so.6
+#2  0x00a5b149 in abort () from /lib/tls/libc.so.6
+#3  0x081435e6 in mono_handle_native_sigsegv (ctx=0xb758bb88) at
+mini-exceptions.c:1026
+#4  0x0812fd1c in sigsegv_signal_handler (_dummy=11, info=0xb758bb08,
+context=0xb758bb88) at mini.c:10360
+#5  <signal handler called>
+#6  sigusr1_signal_handler (_dummy=35, info=0xb758be90, context=0xb758bf10)
+at mini.c:10376
+#7  <signal handler called>
+#8  0x00a197a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+#9  0x00b90cfc in pthread_cond_timedwait@@GLIBC_2.3.2 () from
+/lib/tls/libpthread.so.0
+#10 0x080eec36 in timedwait_signal_poll_cond (cond=0xb7b674d0,
+mutex=0xb7b674b8, timeout=0xb758c2e8) at handles.c:1321
+#11 0x080eed99 in _wapi_handle_timedwait_signal_handle (handle=0x40b,
+timeout=0xb758c2e8) at handles.c:1390
+#12 0x080f2006 in WaitForSingleObjectEx (handle=0x40b, timeout=100,
+alertable=0) at wait.c:189
+#13 0x080e5e4f in mono_monitor_try_enter_internal (obj=0x2ffd8,
+ms=4294967295, allow_interruption=0) at monitor.c:429
+#14 0x080e6125 in mono_monitor_enter (obj=0x0) at monitor.c:481
+#15 0x0809f545 in thread_cleanup (thread=0x21cc0) at threads.c:240
+#16 0x0809fd1a in start_wrapper (data=0x82d2ce8) at threads.c:353
+#17 0x080f4cf2 in thread_start_routine (args=0xb7a174e8) at threads.c:194
+#18 0x080ffd5d in GC_start_routine (arg=0x22f00) at pthread_support.c:1330
+#19 0x00b8e341 in start_thread () from /lib/tls/libpthread.so.0
+#20 0x00af96fe in clone () from /lib/tls/libc.so.6
+
+Expected Results:
+success
+
+How often does this happen? 
+About 60%, depends on the exact timing. If the Sleep line is not commented
+out, the crash never occurs.
+
+Additional Information:
+Occurs on both 1.1.13.6 and 1.1.15. The stack trace comes from the latter.