[Mono-bugs] [Bug 75424][Maj] New - wapi caused build hangs

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Jun 29 18:55:42 EDT 2005


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 bmaurer at users.sf.net.

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

--- shadow/75424	2005-06-29 18:55:42.000000000 -0400
+++ shadow/75424.tmp.740	2005-06-29 18:55:42.000000000 -0400
@@ -0,0 +1,40 @@
+Bug#: 75424
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: io-layer
+AssignedTo: dick at ximian.com                            
+ReportedBy: bmaurer at users.sf.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: wapi caused build hangs
+
+On x86-mono, the build was hung due to a .wapi file that seems to have been
+corrupt. You should be able to reproduce by:
+
+Using the attached .wapi files (changing the host name)
+Running mcs
+
+The stack trace I got from gdb was:
+
+(gdb) bt
+#0  0xffffe410 in ?? ()
+#1  0xbfffd608 in ?? ()
+#2  0x00000008 in ?? ()
+#3  0x4d522b18 in ?? ()
+#4  0x401a805b in semget () from /lib/tls/libc.so.6
+#5  0x081a9a5c in ?? ()
+#6  0x4d522b18 in ?? ()
+#7  0x081ac1f0 in _wapi_global_signal_cond ()
+#8  0xbfffd688 in ?? ()
+#9  0x080f1868 in mono_pthread_key_for_tls ()
+Previous frame inner to this frame (corrupt stack?)
+
+Dunno what caused this weird stack stuff.


More information about the mono-bugs mailing list