[Mono-bugs] [Bug 78241][Nor] Changed - CreateThread failure/out of wapi handles slots

[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 robertj at gmx.net.

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

--- shadow/78241	2006-05-25 10:55:03.000000000 -0400
+++ shadow/78241.tmp.27457	2006-05-25 12:36:39.000000000 -0400
@@ -1,15 +1,15 @@
 Bug#: 78241
 Product: Mono: Runtime
 Version: 1.1
 OS: SUSE 9.0
 OS Details: Linux 2.4.21-303-smp4G #1 SMP Tue Dec 6 12:33:10 UTC 2005 i686 i686 i386 GNU/Linux
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
-Priority: Major
+Priority: Normal
 Component: io-layer
 AssignedTo: dick at ximian.com                            
 ReportedBy: robertj at gmx.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
@@ -695,6 +695,69 @@
 ------- Additional Comments From robertj at gmx.net  2006-05-17 03:42 -------
 Dick, null.exe should exist. See my message (null.cs)
 
 
 ------- Additional Comments From dick at ximian.com  2006-05-25 10:55 -------
 Fixed again.
+
+------- Additional Comments From robertj at gmx.net  2006-05-25 12:36 -------
+There are 2 issues with the patch:
+
+1) on a non-NPTL system runing the 1-1-13 branch I got now and then
+
+** (null.exe:3036): WARNING **: _wapi_thread_abandon_mutexes: error
+looking up thread handle 0x408
+
+** (null.exe:3036): WARNING **: thread_set_termination_details: error
+looking up thread handle 0x408
+
+while running the proc.exe/null.exe test.
+
+It's always handle 0x408 and it's always reproducible.
+
+
+
+2) on a x86_64 NTPL system running Mono HEAD I encountered
+   segfaults from null.exe, if Environment.Exit () was used,
+   like here:
+
+// null.cs
+class T { static void Main () { System.Environment.Exit (1); } }
+
+
+Stack trace:
+
+** ERROR **: file critical-sections.c: line 89
+(DeleteCriticalSection): assertion failed: (ret == 0)
+aborting...
+
+=================================================================
+Got a SIGABRT while executing native code. This usually indicates
+a fatal error in the mono runtime or one of the native libraries
+used by your application.
+=================================================================
+
+Stacktrace:
+
+in (wrapper managed-to-native) System.Environment:Exit (int) <0xb>
+in (wrapper managed-to-native) System.Environment:Exit (int)
+<0xffffffffffffffa5>
+in T:Main () <0xd>
+in (wrapper runtime-invoke) System.Object:runtime_invoke_void
+(object,intptr,intptr,intptr) <0xffffffffc04e2cd2>
+
+Native stacktrace:
+
+        /usr/local/bin/mono(mono_handle_native_sigsegv+0x99) [0x50e389]
+        /lib64/tls/libpthread.so.0 [0x2a95c0f650]
+        /lib64/tls/libc.so.6(gsignal+0x39) [0x2a95fa6479]
+        /lib64/tls/libc.so.6(abort+0x13f) [0x2a95fa7abf]
+        /opt/gnome/lib64/libglib-2.0.so.0 [0x2a959a56b6]
+        /opt/gnome/lib64/libglib-2.0.so.0(g_log+0x83) [0x2a959a5743]
+        /usr/local/bin/mono [0x4be85a]
+        /usr/local/bin/mono(mono_thread_cleanup+0x1a) [0x47313a]
+        /usr/local/bin/mono(mono_runtime_cleanup+0x18) [0x477398]
+        /usr/local/bin/mono [0x4ddd76]
+        /usr/local/bin/mono(mono_runtime_quit+0x23) [0x475be3]
+        /usr/local/bin/mono [0x49d682]
+        [0x40017b3d]
+