[Mono-bugs] [Bug 51278][Nor] New - Mint failures on MacOS 10.3.1

[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 peter@ximian.com.

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

--- shadow/51278	2003-11-21 16:57:08.000000000 -0500
+++ shadow/51278.tmp.6405	2003-11-21 16:57:08.000000000 -0500
@@ -0,0 +1,65 @@
+Bug#: 51278
+Product: Mono/Runtime
+Version: unspecified
+OS: 
+OS Details: MacOS 10.3.1
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: peter@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Mint failures on MacOS 10.3.1
+
+I'm having trouble creating an xml-rpc service on MacOS 10.3.  I've built mint without 
+garbage collection support (libboehm is broken on 10.3 so far).  The service runs, but as 
+soon as I make an rpc call it dies with an infinite loop of this output:
+
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+(xsp.exe:13261): GLib-WARNING **: poll(2) failed due to: Bad file descriptor.
+
+On the client side, I get this stack trace:
+Unhandled Exception: System.ExecutionEngineException: No GCHandle support built-in
+#0: 0x00000            in System.Runtime.InteropServices.GCHandle::GetTargetHandle ([O:
+0x2574250] [0] [0] )
+#1: 0x00004 call       in System.Runtime.InteropServices.GCHandle::.ctor ([O:0x2574250] [0] 
+)
+#2: 0x00004 call       in System.Runtime.InteropServices.GCHandle::Alloc ([O:0x2574250] [0] 
+)
+#3: 0x00020 call       in System.WeakReference::AllocateHandle ([O:0x2574250] )
+#4: 0x0000f callvirt   in System.WeakReference::.ctor ([O:0x2574250] [0] )
+#5: 0x00003 call       in System.WeakReference::.ctor ([O:0x2574250] )
+#6: 0x0009e newobj     in System.Net.WebConnectionGroup::CreateOrReuseConnection ()
+#7: 0x000b3 callvirt   in System.Net.WebConnectionGroup::GetConnection ()
+#8: 0x00011 callvirt   in System.Net.ServicePoint::SendRequest ([O:0x25502c0] [O:
+0x6276b0] )
+#9: 0x00129 callvirt   in System.Net.HttpWebRequest::BeginGetRequestStream ([O:0x0] [O:
+0x0] )
+#10: 0x00003 callvirt   in System.Net.HttpWebRequest::GetRequestStream ()
+#11: 0x0004a callvirt   in CookComputing.XmlRpc.XmlRpcClientProtocol::Invoke ([O:
+0x66ef40] [O:0x69a0c0] [O:0x69a110] )
+#12: 0x00004 call       in CookComputing.XmlRpc.XmlRpcClientProtocol::Invoke ([O:
+0x69a0c0] [O:0x69a110] )
+#13: 0x0000c callvirt   in .HelloProxy::hello ()
+#14: 0x00007 callvirt   in .Hello::Main ()
+
+The client side problem looks like it may be related to being built without GC support, but 
+the server problem is troubling.  It has the same problem if I try the rpc call from a python 
+client.
+
+I've attached a tarball with a test case.  To run the server, run "mint xsp.exe".  To run the 
+client, run "mint HelloClient.exe".  The expected output is "Hello World!" from the client.
+
+Both the server and client work fine on Linux.