When.com Web Search

  1. Ad

    related to: 2038 code problems list

Search results

  1. Results From The WOW.Com Content Network
  2. Year 2038 problem - Wikipedia

    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 computing problem that leaves some computer systems unable to represent times after 03:14:07 UTC on 19 January 2038.

  3. Time formatting and storage bugs - Wikipedia

    en.wikipedia.org/wiki/Time_formatting_and...

    The Network Time Protocol has an overflow issue related to the Year 2038 problem, which manifests itself at 06:28:16 UTC on 7 February 2036, rather than 2038. The 64-bit timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving NTP a time scale that rolls over every 2 32 seconds (136 years) and ...

  4. List of software bugs - Wikipedia

    en.wikipedia.org/wiki/List_of_software_bugs

    A similar problem will occur in 2038 (the year 2038 problem), as many Unix-like systems calculate the time in seconds since 1 January 1970, and store this number as a 32-bit signed integer, for which the maximum possible value is 2 31 − 1 (2,147,483,647) seconds. [50] 2,147,483,647 seconds equals 68 years, and 2038 is 68 years forward from 1970.

  5. Epoch (computing) - Wikipedia

    en.wikipedia.org/wiki/Epoch_(computing)

    Many Unix-like operating systems which keep time as seconds elapsed from the epoch date of 1 January 1970, and allot timekeeping enough storage to store numbers as large as 2 147 483 647 will experience an overflow problem on 19 January 2038. This is known as the Year 2038 problem.

  6. GPS week number rollover - Wikipedia

    en.wikipedia.org/wiki/GPS_week_number_rollover

    The GPS week number rollover is a phenomenon that happens every 1,024 weeks, which is about 19.6 years. The Global Positioning System (GPS) broadcasts a date, including a week number counter that is stored in only ten binary digits, whose range is therefore 0–1,023.

  7. Category:2038 - Wikipedia

    en.wikipedia.org/wiki/Category:2038

    Year 2038 problem This page was last edited on 30 September 2024, at 10:08 (UTC). Text is available under the Creative ... Code of Conduct; Developers; Statistics;

  8. System time - Wikipedia

    en.wikipedia.org/wiki/System_time

    Many implementations that currently store system times as 32-bit integer values will suffer from the impending Year 2038 problem. These time values will overflow ("run out of bits") after the end of their system time epoch, leading to software and hardware errors.

  9. Category:Future problems - Wikipedia

    en.wikipedia.org/wiki/Category:Future_problems

    Year 2038 problem This page was last edited on 9 April 2023, at 16:06 (UTC). Text is available under the Creative ... Code of Conduct; Developers; Statistics;