Year 2038 problem

FanJ · Jul 30, 2023

2038. Well, still some 15 years to go. Not the same as the "Millenium bug". But nevertheless be aware of it.

https://en.wikipedia.org/wiki/Year_2038_problem

The year 2038 problem (also known as Y2038,[1] Y2K38, Y2K38 superbug or the Epochalypse[2][3]) is a time formatting bug in computer systems with representing times after 03:14:07 UTC on 19 January 2038.
Click to expand...

The problem exists in systems which measure Unix time – the number of seconds elapsed since the Unix epoch (00:00:00 UTC on 1 January 1970) – and store it in a signed 32-bit integer. The data type is only capable of representing integers between −(2³¹) and 2³¹ − 1, meaning the latest time that can be properly encoded is 2³¹ − 1 seconds after epoch (03:14:07 UTC on 19 January 2038 ). Attempting to increment to the following second (03:14:08 ) will cause the integer to overflow, setting its value to −(2³¹) which systems will interpret as 2³¹ seconds before epoch (20:45:52 UTC on 13 December 1901). The problem is similar in nature to the year 2000 problem.
Click to expand...

Read there more!
I'm sure that in the coming years there will be more posts about this.

Log in or Sign up

Year 2038 problem

FanJ Updates Team

Log in or Sign up

Year 2038 problem

FanJ Updates Team

Useful Searches