[Mono-bugs] [Bug 51506][Wis] New - System.Environment.TickCount should only return nonnegative values

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sun, 30 Nov 2003 02:39:18 -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 mass@akuma.org.

http://bugzilla.ximian.com/show_bug.cgi?id=51506

--- shadow/51506	2003-11-30 02:39:18.000000000 -0500
+++ shadow/51506.tmp.28817	2003-11-30 02:39:18.000000000 -0500
@@ -0,0 +1,29 @@
+Bug#: 51506
+Product: Mono/MCS
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: mass@akuma.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: System.Environment.TickCount should only return nonnegative values
+
+per the MSDN documentation, System.Environment.TickCount should never go
+negative. My understanding is that by not processing that unsigned int
+returned by GetTickCount, you allow it to go negative half of the time.
+
+Unfortunately there isn't an easy way to reproduce this, as the value would
+only be negative half the time, changing every 25 days.
+
+also per the MSDN documentation, the value "overflows to zero", I suspect
+this ambiguous statement means that the high bit is just always clear and
+the # wraps at 24.8 days, not that between 25 and 50 days after reboot the
+value returned is always zero.