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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=75436 --- shadow/75436 2005-09-28 10:51:23.000000000 -0400 +++ shadow/75436.tmp.31993 2005-09-30 13:00:30.000000000 -0400 @@ -147,6 +147,18 @@ Any progress or work-arounds on this? It's a show-stopper for me. ------- Additional Comments From [EMAIL PROTECTED] 2005-09-28 10:51 ------- FYI, the test also fails with svn head on panther. Looking into it... + +------- Additional Comments From [EMAIL PROTECTED] 2005-09-30 13:00 ------- +Here's a potential patch for the non-blocking sockets calling +connect() twice issue on macos. I'd like Gonzalo's second opinion as +well before I commit. + +There is another problem going in with this bug if the socket is in +blocking mode, and also in bug 75558, in that the async method doesn't +seem to be being called on macos. Still looking at that part. + +(There's a runtime patch too to give the correct error number when the +async connect fails, but that's not needed to test this patch.) _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
