Search
Search titles only
By:
Search titles only
By:
Log in
Register
Search
Search titles only
By:
Search titles only
By:
Menu
Install the app
Install
Forums
New posts
All threads
Latest threads
New posts
Trending threads
Trending
Search forums
What's new
New posts
New ads
New profile posts
Latest activity
Free Ads
Latest reviews
Search ads
Members
Current visitors
New profile posts
Search profile posts
Contact us
Latest ads
Baseus PI LITE INDOOR CAMERA
ErMurazor
Updated:
Yesterday at 12:26 PM
Ad icon
Colombo
Hard Disk For Sale
mazza
Updated:
Saturday at 10:23 PM
land for sale
justasking
Updated:
Saturday at 9:32 AM
AMD AM 5 Ryzen setup
prabodhamadusanka
Updated:
Thursday at 12:56 PM
Gampaha
ACER OKW223 Wired RGB Keyboard
chint
Updated:
Thursday at 10:17 AM
Electronics
Vehicles
Property
Search
Reply to thread
Forums
General
ElaKiri Talk!
Old Computers Magazines
Get the App
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="EKGuest" data-source="post: 28482360" data-attributes="member: 582168"><p>The concept is simple - this bug occurs due to a concept called integer overflow in programming. For example in C# in a variable of sbyte data type (which is a signed 8-bit integer) the maximum value that can be stored is 127. If you add 1 to it instead of storing 128 it will store -128. This bug occurs in systems that uses 32 bits to represent time as a whole number(a signed 32-bit integer) - the number of seconds elapsed since 1970-01-01 00:00:00. The maximum value a 32 bit integer can represent is 2147483647, and if you add 1 to it instead of storing 2147483648 it will store -2147483648.</p><p></p><p>2147483647 represents 2038-01-19 03:14:07 UTC. If you add 1 to it instead of representing 2038-01-19 03:14:08 UTC it will represent 1901-12-13 20:45:52 UTC.</p><p></p><p>If some system used 8-bit signed integers to store time, this bug would occur 2 minutes and 8 seconds after 1970-01-01 00:00:00 UTC, as the maximum time an 8-bit signed integer can represent is 1970-01-01 00:02:07 UTC</p></blockquote><p></p>
[QUOTE="EKGuest, post: 28482360, member: 582168"] The concept is simple - this bug occurs due to a concept called integer overflow in programming. For example in C# in a variable of sbyte data type (which is a signed 8-bit integer) the maximum value that can be stored is 127. If you add 1 to it instead of storing 128 it will store -128. This bug occurs in systems that uses 32 bits to represent time as a whole number(a signed 32-bit integer) - the number of seconds elapsed since 1970-01-01 00:00:00. The maximum value a 32 bit integer can represent is 2147483647, and if you add 1 to it instead of storing 2147483648 it will store -2147483648. 2147483647 represents 2038-01-19 03:14:07 UTC. If you add 1 to it instead of representing 2038-01-19 03:14:08 UTC it will represent 1901-12-13 20:45:52 UTC. If some system used 8-bit signed integers to store time, this bug would occur 2 minutes and 8 seconds after 1970-01-01 00:00:00 UTC, as the maximum time an 8-bit signed integer can represent is 1970-01-01 00:02:07 UTC [/QUOTE]
Insert quotes…
Verification
Hath warak paha keeyada? (hatha wadikireema paha)
Post reply
Top
Bottom