[Mono-bugs] [Bug 72740][Maj] Changed - Deadlock with Thread.Abort

[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 vargaz@gmail.com.

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

--- shadow/72740	2005-02-18 16:12:01.000000000 -0500
+++ shadow/72740.tmp.22755	2005-03-17 07:17:48.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 72740
 Product: Mono: Runtime
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Major
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: bmaurer@users.sf.net               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -47,6 +47,25 @@
 	{
 		while (true) {
 			Type [] x = typeof (object).Assembly.GetTypes ();
 		}
 	}
 }
+
+------- Additional Comments From vargaz@gmail.com  2005-03-17 07:17 -------
+This seems to be caused by this line in sigusr1_signal_handler ()
+in mini.c:
+
+	running_managed = (mono_jit_info_table_find (mono_domain_get (),
+mono_arch_ip_from_context(ctx)) != NULL);
+
+The jit_info_table_find () function acquires the domain lock, and
+the pthread locking functions are not async safe, so they should only
+be invoked from a signal handler if it is guaranteed that the code
+interrupted by the signal is not inside another POSIX function. 
+For the abort signal this is not true, since it can be
+delivered while a thread is in pthread_mutex_lock () / unlock ().
+
+
+
+
+