Year 2038 Problem

The year 2038 problem may cause some computer software to fail at some point near the year 2038. The problem affects all software and systems that both store system time as a signed 32-bit integer, and interpret this number as the number of seconds since 00:00:00 UTC on Thursday, 1 January 1970. The furthest time that can be represented this way is 03:14:07 UTC on Tuesday, 19 January 2038. Times beyond this moment will "wrap around" and be stored internally as a negative number, which these systems will interpret as a date in 1901 rather than 2038. This is caused by integer overflow. The counter "runs out" of usable digits, "increments" the sign bit instead, and reports a maximally negative number (continuing to count up, toward zero). This is likely to cause problems for users of these systems due to erroneous calculations.

Further, while most programs will only be affected in or very close to 2038, programs that work with future dates will begin to run into problems much sooner. For example, a program that works with dates 20 years in the future will have to be fixed no later than 2018.

Because most 32-bit Unix-like systems store and manipulate time in this format, it is usually called Unix time, and so the year 2038 problem is often referred to as the Unix Millennium Bug.

Read more about Year 2038 ProblemEarly Problems, Vulnerable Systems, Data Structures With Time Problems, Solutions

Other articles related to "year 2038 problem, 2038, problem, year, problems, years":

Y2K Problem - Programming Problem - Date Bugs Similar To Y2K - Year 2038 Problem
... During and after 2038, this number will exceed 231 − 1, the largest number representable by a signed 32-bit integer, causing the Year 2038 problem (also known ... To solve this problem, many systems and languages have switched to a 64-bit timestamp, or supplied alternatives which are 64-bit ...
2038 - In Fiction - Film and Television
... to Futurama, petroleum reserves run dry during this year ... The 1989 Japanese movie Gunhed takes place in this year ...
Year 2038 Problem - Solutions
... There is no universal solution for the Year 2038 problem ... the time_t data type would result in code compatibility problems in any application in which date and time representations are dependent on the nature of the signed 32-bit time_t integer ... For example, changing time_t to an unsigned 32-bit integer, which would extend the range to the year 2106, would adversely affect programs that store, retrieve, or manipulate dates ...
Unix - Impact - 2038
... On 19 January 2038 on 32 bit Unix systems, the current time will roll over from a zero followed by 31 ones (0x7FFFFFFF) to a one followed by 31 zeros (0x80000000 ... However, such a kludge merely postpones the problem to 7 February 2106, and could introduce bugs in software that computes time differences ... that the OS itself and 64-bit applications will correctly handle dates for some 292 billion years ...

Famous quotes containing the words problem and/or year:

    War is not a life: it is a situation,
    One which may neither be ignored nor accepted,
    A problem to be met with ambush and stratagem,
    Enveloped or scattered.
    —T.S. (Thomas Stearns)

    You can feel it, in a hundred little ways year after year. It is so certain and inevitable, that the next century will be a time in which it is not simply safe, but commonplace, to be openly gay.
    Anna Quindlen (b. 1952)