[Mono-bugs] [Bug 41193][Maj] Changed - stream.BeginRead(...) blocks if no data is present.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 18 Mar 2005 22:59:30 -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 mmurray@deepthought.org.


--- shadow/41193	2003-04-11 19:13:54.000000000 -0400
+++ shadow/41193.tmp.31902	2005-03-18 22:59:30.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 41193
-Product: Mono/Class Libraries
+Product: Mono: Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: RESOLVED   
-Resolution: NOTABUG
+Status: REOPENED   
 Severity: Unknown
 Priority: Major
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: kuhne@wanadoo.es               
 QAContact: mono-bugs@ximian.com
@@ -72,6 +72,28 @@
 Waiting user response
 ~ $ mono ./bug41193.exe
 User input readed
 Waiting user response
+------- Additional Comments From mmurray@deepthought.org  2005-03-18 22:59 -------
+Running the example on windows under v2.0.40607, the application would
+terminate immediately after displaying the line "Waiting user
+response". I added a Thread.Sleep(300); after the Console.WriteLine().
+Now, I see the following output:
+Waiting for user response
+User input readed
+Hence, I am reopening the bug, because I believe the original
+behavior, reproduceable on v1.1.4322, is incorrect. BeginRead() is
+hardly asynchronous if it blocks. EndRead() is supposed to block until
+there is data ready to be read, according to the documentation. The
+documentation makes no statement that BeginRead() will block, but does
+describe it as an asynchronous operation which implies that it should
+not block.