[Mono-bugs] [Bug 58065][Cri] Changed - Random Crash or Freeze running gacutil
Fri, 7 May 2004 09:28:31 -0400 (EDT)
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 firstname.lastname@example.org.
--- shadow/58065 2004-05-06 16:02:45.000000000 -0400
+++ shadow/58065.tmp.29912 2004-05-07 09:28:31.000000000 -0400
@@ -55,6 +55,18 @@
#8 0x000018ec in _start (argc=459912, argv=0x70548, envp=0x1) at /SourceCache/Csu/Csu
#9 0x8fe1a58c in __dyld__dyld_start ()
------- Additional Comments From email@example.com 2004-05-06 16:02 -------
A good test case showing similar crash/hand/failure is threadpool.exe in mono/tests.
+------- Additional Comments From firstname.lastname@example.org 2004-05-07 09:28 -------
+threadpool is demonstrating a different problem I think - it's failing
+because ThreadPool cleans up by Thread.Abort()ing all the runner
+threads, and our Thread.Abort is extremely unstable (I assume on all
+platforms, it certainly is on x86.)
+I can reproduce this deadlock on ppc by running a simple "Hello,
+World!" enough times in a loop...
+I'm going to try valgrind's thread debugging skin on a rh9/nptl box,
+to see if it throws up anything likely.