When.com Web Search

  1. Ad

    related to: 2038 code problems examples

Search results

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

    en.wikipedia.org/wiki/Year_2038_problem

    There is no universal solution for the Year 2038 problem. For example, in the C language, 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.

  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. Talk:Year 2038 problem/Archive 2 - Wikipedia

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

    The 2038 problem is primarily a UNIX problem, but it also occurs in any program that uses the same Epoch. the same Tick and the same number of bits as Unix. The program does not have to be an operating system; although many programs simply use the same format as the underlying OS, others calculate dates internally.

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

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

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

    Main page; Contents; Current events; Random article; About Wikipedia; Contact us