Year 2038 problem - Wikipedia
网页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.
Year 2038 Problem: What Will Happen In 2038? - Science ABC
网页2024年6月2日 · The 2038 problem refers to the time encoding error that will occur in the year 2038 in 32-bit systems. This may cause havoc in machines and services that use time to encode instructions and licenses. The effects will primarily be seen in devices that are not connected to the internet.
What is the Year 2038 problem? - HowStuffWorks
网页2024年5月17日 · 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, the epoch date for Unix systems.
2038 Bug Survival Guide: Lessons From Leap Year Code Issues
网页2024年2月19日 · The 2038 bug, also known as the Unix Millennium Bug or Y2K38, is a problem that arises from the way some systems store and represent date and time values using a number called a timestamp. A timestamp is the number of seconds that have passed since January 1, 1070, which is called the Unix epoch.
What is the "2038 Effect", what devices does it affect and what …
网页2021年9月18日 · The problem of the year 2038 is due to the maximum bit capacity of 32-bit systems. They store memory and execute their processes using 32 binary digits, which can be represented by a 1 or a 0, allowing a total of 4,294,967,296 possible combinations.
What is the Year 2038 Problem? A Modern-Day Time Bomb - EMB …
网页2024年7月26日 · The Year 2038 Problem, sometimes referred to as the Y2K38 bug, is a potential issue for computer systems that use a particular method of timekeeping. Much like the Y2K problem, which arose as the year 2000 approached, this issue could cause significant disruptions if not addressed.
Year 2038 Bug: What is it? How to solve it? - Stack Overflow
网页2023年4月25日 · The year 2038 problem (also known as Unix Millennium Bug, Y2K38 by analogy to the Y2K problem) 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 UTC on …
The Year 2038 Problem - Roger M. Wilcox
网页2003年10月23日 · The greatest danger with the Year 2038 Problem is its invisibility. The more-famous Year 2000 is a big, round number; it only takes a few seconds of thought, even for a computer-illiterate person, to imagine what might happen when 1999 turns into 2000. But January 19, 2038 is not nearly as obvious.
Are you prepared for the Unix 2038 problem? - TechTarget
网页2008年5月21日 · If you use a Unix- or Linux-based system, there's one more date-related bug you'll need to worry about -- in the year 2038. All 32-bit Unix/Linux-based systems store the system clock time internally as the number of seconds since the Epoch, or 00:00:00 on January 1, 1970.
Y2K - What Was Y2K - Year 2038 Problem - Popular Mechanics
网页2020年1月7日 · The crisis programmers really fear is in 2038, when systems running C will run out of dates. Twenty years after we thought we were in the clear, New Scientist reports that a desperate fix for the...
跳至内容