为您找到"
Y2038
"相关结果约100,000,000个
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.
What Is The Year 2038 Problem? Also known as the Y2K38 Bug, The Unix Y2K Bug or Epochalypse. The year 2038 problem is a problem caused by how some software systems store dates.
Year 2038 is a common problem for programs written in C programming language. Lawrence Lawry / Getty Images. Advertisement. Key Takeaways. The Year 2038 problem occurs because C programming utilizes a 4-byte integer to store time data, which will overflow on January 19, 2038.; This overflow happens due to the 4-byte signed integer's maximum limit of 2,147,483,647 seconds after January 1, 1970 ...
For Y2038 planning, an incremental and proactive approach is needed at this stage. Right now, some areas to focus on include: 1) software dealing with future times and dates; 2) on-the-wire message and file formats; 3) devices with long deployed lifetimes and their dependencies.
The 2038 problem refers to the time encoding error that will occur in the year 2038 in 32-bit systems, such as UNIX. This may cause havoc in machines and services that use time to encode instructions and licenses, especially in devices that are not connected to the internet.
14.5 Avoiding the year 2038 problem ¶. The year 2038 problem denotes unpredictable behaviour that will likely occur in the year 2038, for programs that use a 32-bit signed integer 'time_t' type that cannot represent timestamps on or after 2038-01-19 03:14:08 UTC.See Year 2038 problem for details. The Gnulib module 'year2038' fixes this problem on some platforms, by making time_t wide ...
The Y2038 bug is a computer bug that is related to the way that computers store and handle dates. It is also known as the "Year 2038 problem", the "Unix Millennium bug", or the "Epochalypse". How does a computer store a date? To store a date, computers use a numerical value to represent the year, month, day, hours, minutes and seconds. ...
The year 2038 problem (also known as Unix Millennium bug, or Y2K38 by analogy to the Y2K problem, known as the millennium bug) may cause some computer software to fail before or in the year 2038. The problem affects all software and systems that store system time as a signed 32-bit integer, and interpret this number as the number of seconds since 00:00:00 January 1, 1970. [1]
By the year 2038, the time_t representation for the current time will be over 2 140 000 000. And that's the problem. A modern 32-bit computer stores a "signed integer" data type, such as time_t, in 32 bits.The first of these bits is used for the positive/negative sign of the integer, while the remaining 31 bits are used to store the number itself.
Y2038.com also offers premium Y2038-related services, including general consultation, contract labor for help with assessment and mitigation, and training. We also help with other computer date issues, such as the NTP issue in 2036 (Y2036), the Mac OS date rollover issue in 2040 (Y2040), and the IBM z/OS date rollover issue in 2042 (Y2042). ...