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=79395 --- shadow/79395 2006-09-13 18:40:34.000000000 -0400 +++ shadow/79395.tmp.9111 2006-09-13 18:40:34.000000000 -0400 @@ -0,0 +1,44 @@ +Bug#: 79395 +Product: Mono: Class Libraries +Version: 1.1 +OS: GNU/Linux [Other] +OS Details: Debian Unstable +Status: NEW +Resolution: +Severity: +Priority: Blocker +Component: System +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: serial port blcoking read with timeout seems broken + +Please fill in this template when reporting a bug, unless you know what you +are doing. +Description of Problem: +With the PosixHelper lib (libmono0_1.1.17-2) installed and using: +read_serial(unixFd, buffer, offset, count, readTimeout) +to make blocking serial port read calls does not properly honor the +requested timeout (anymore). +Also, the behavior of the Parity enumeration has changed, but this appears +to be intentional (to match .NET2.0)?? + +Steps to reproduce the problem: +Do a blocking read with a non-zero timeout when no data has actually been +received. + +Actual Results: +It blocks forever. + +Expected Results: +It should return with a timeout indication (received character count = 0) + +How often does this happen? +Every time. + +Additional Information: +A different recent version (libmono0_1.1.17-1) seemed to have a related +bug, where the read would not block at all (with a non-zero timeout parameter). _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
