---- Reported by bmaurer@users.sf.net 2005-04-24 14:38:07 MST ----

using System;
using System.Threading;
public class Test {
	static Thread t = null;
	static void Main ()
	{
		while (true) {
			new Test ();
			if (t != null)
				t.Abort ();
		}
	}
	
	~ Test ()
	{
		Console.Write (".");
		if (t == null)
			t = Thread.CurrentThread;
	}
}


On this test case, we print a few dots, and then stop. On msft, the dots
get printed forever.

Note that if the abort is requested from inside the finalizer thread, we
seem to catch the abort correctly.



---- Additional Comments From gonzalo@ximian.com 2005-04-24 16:51:59 MST ----

I cannot reproduce this.



---- Additional Comments From bmaurer@users.sf.net 2005-04-24 19:14:13 MST ----

I can only get this on my hyperthreaded box, on a single cpu, it does
not trigger.



---- Additional Comments From bmaurer@users.sf.net 2005-04-24 19:15:50 MST ----

It looks like we aren't actually aborting the finalizer thread -- the
entire program deadlocks. But this is very different than the other
deadlock-on-abort bugs because I can only repo on an smp



---- Additional Comments From vargaz@gmail.com 2005-04-26 10:07:09 MST ----

This is the usual 'taking locks inside signal handlers leads to
deadlock' issue.





---- Additional Comments From bmaurer@users.sf.net 2005-06-29 15:05:21 MST ----

All the stack traces I can see look like a dup of that...

*** This bug has been marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=MONO58065 ***


Unknown operating system unknown. Setting to default OS "Other".
This bug was marked DUPLICATE in the database it was moved from.
    Changing resolution to "MOVED"