[Mono-bugs] [Bug 53168][Blo] Changed - Operation on non-blocking socket would block

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sat, 24 Jan 2004 09:44:12 -0500 (EST)

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 mikeg_us@hotmail.com.


--- shadow/53168	2004-01-24 09:39:47.000000000 -0500
+++ shadow/53168.tmp.7620	2004-01-24 09:44:12.000000000 -0500
@@ -1,12 +1,12 @@
 Bug#: 53168
 Product: Mono/Class Libraries
 Version: unspecified
 OS: Red Hat 8.0
 OS Details: 
-Status: NEEDINFO   
+Status: REOPENED   
 Severity: Unknown
 Priority: Blocker
 Component: System
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: mikeg_us@hotmail.com               
@@ -106,6 +106,18 @@
 I cannot do much with the code. Can you attach a self contained test case?
 ------- Additional Comments From mikeg_us@hotmail.com  2004-01-24 09:39 -------
 Created an attachment (id=6513)
 test case to cause bug
+------- Additional Comments From mikeg_us@hotmail.com  2004-01-24 09:44 -------
+Compile TcpFlood.cs test case.  Run from two different consoles.  
+Start one as "mono TcpFlood.exe" and the other as "mono TcpFlood.exe 
+localhost 3465" (or whatever port the first one reports as listening 
+on).  If run using Mono, I get the SocketException: Operation on non-
+blocking socket would block.  If compiled/run using MS .NET 1.0 
+framework, no exception is thrown and the run eventually completes