[Mono-bugs] [Bug 75705][Nor] Changed - Receive on closed socket behaviour different between windows and linux.

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri May 4 17:50:08 EDT 2007

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 latexer at gentoo.org.


--- shadow/75705	2007-04-24 12:52:12.000000000 -0400
+++ shadow/75705.tmp.15012	2007-05-04 17:50:08.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 75705
 Product: Mono: Class Libraries
 Version: 1.1
 OS: other
 OS Details: Windows-XP-5.1.2600 & Linux-2.6.8-2-k7-i686-with-debian-3.1
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
 Severity: Unknown
 Priority: Normal
 Component: System
 AssignedTo: dick at ximian.com                            
 ReportedBy: Nev at Delap.com               
 QAContact: mono-bugs at ximian.com
@@ -113,6 +113,32 @@
 "System.Net.Sockets.SocketException : The socket is not connected"
 ------- Additional Comments From dick at ximian.com  2007-04-24 12:52 -------
 Fixed in svn r76193
+------- Additional Comments From latexer at gentoo.org  2007-05-04 17:50 -------
+I need to re-open this, with this patch in SVN, our middleware
+component at work is bombing in a tcpclient.GetStream ().Read call
+with the following exception:
+System.IO.IOException: Read failure --->
+System.Net.Sockets.SocketException: interrupted
+  at System.Net.Sockets.Socket.Receive (System.Byte[] buf, Int32
+offset, Int32 size, SocketFlags flags) [0x000b0] in
+  at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer,
+Int32 offset, Int32 size) [0x00050] in
+--- End of inner exception stack trace ---
+  at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer,
+Int32 offset, Int32 size) [0x00066] in
+  at
+() [0x00035] in
+Reverting just r76193 stops the problem, and everything works as
+expected. I can attempt to create a small test case if it would help.

More information about the mono-bugs mailing list