[Mono-bugs] [Bug 76374][Nor] Changed - Binary.PeekChar Bug
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Tue Nov 1 03:00:14 EST 2005
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 zac at zacbowling.com.
http://bugzilla.ximian.com/show_bug.cgi?id=76374
--- shadow/76374 2005-10-10 18:48:18.000000000 -0400
+++ shadow/76374.tmp.31966 2005-11-01 03:00:14.000000000 -0500
@@ -1,12 +1,12 @@
Bug#: 76374
Product: Mono: Class Libraries
Version: 1.1
OS: unknown
OS Details:
-Status: NEW
+Status: ASSIGNED
Resolution:
Severity: Unknown
Priority: Normal
Component: System
AssignedTo: mono-bugs at ximian.com
ReportedBy: gonzaloantonio at gmail.com
@@ -65,6 +65,15 @@
How often does this happen?
any time.
------- Additional Comments From gonzaloantonio at gmail.com 2005-10-10 18:48 -------
This bug only occurs with files over 500 KB size.
+
+------- Additional Comments From zac at zacbowling.com 2005-11-01 03:00 -------
+It is a bug, but its not safe to use the char functions on the binary
+reader. I'm guessing that because we default to utf-8 like ms.net, if
+the byte at where ever the buffer is at, is above 128, in UTF-8 that
+would need to keep rolling over and does so until it hits something
+looking for something else and borks. It looks pretty safe but the
+error is up inside System.Text somewhere. Can you post the image you
+where using so I can duplicate this exactly?
More information about the mono-bugs
mailing list