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

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 12 Apr 2005 21:32:31 -0400 (EDT)

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.


--- shadow/51506	2005-04-12 21:32:31.000000000 -0400
+++ shadow/51506.tmp.23609	2005-04-12 21:32:31.000000000 -0400
@@ -0,0 +1,41 @@
+Bug#: 51506
+Product: Mono: Compilers
+Version: unspecified
+OS: unknown
+OS Details: 
+Status: CLOSED   
+Severity: Unknown
+Priority: Wishlist
+Component: C#
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: mass@akuma.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+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.
+------- Additional Comments From gonzalo@ximian.com  2003-11-30 11:57 -------
+It's easy to reproduce. Just get the piece of code in TickCounts and
+return the values you thing are wrong after casting them to uint.
+------- Additional Comments From miguel@ximian.com  2003-12-13 06:38 -------
+I do not understand this report.
+Can you be more specific?  What is the problem that yo usee?
+Am setting this bug to NEEDINFO, please reset it once you have the
+extra data.