When.com Web Search

  1. Ad

    related to: 2038 code problems

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. 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.

  5. 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.

  6. Talk:Year 2038 problem/Archive 2 - Wikipedia

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

    There is no universal solution for the Year 2038 problem. Any change to the definition of 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.

  7. 2,147,483,647 - Wikipedia

    en.wikipedia.org/wiki/2,147,483,647

    The latest time that can be represented in this form is 03:14:07 UTC on Tuesday, 19 January 2038 (corresponding to 2,147,483,647 seconds since the start of the epoch). This means that systems using a 32-bit time_t type are susceptible to the Year 2038 problem. [9]

  8. Talk:Year 2038 problem/Archive 1 - Wikipedia

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

    1 Year 2038 problem. 2 C/C++. 5 comments. 3 Deletions. 2 comments. 4 ... 5 Redundancy. 1 comment. 6 1901? 3 comments. 7 Year 292,471,208,678 problem. 11 comments. 8 ...

  9. Category:Future problems - Wikipedia

    en.wikipedia.org/wiki/Category:Future_problems

    Upcoming problems with a great possibility that these problems occur, or topics dealing with solving such problems. ... Year 2038 problem ... Code of Conduct;