Why we’ll never see time travellers of the 80s in year 2038
summary
Systems using 32-bit signed time_t maxing at 2,147,483,647 seconds overflow on January 19 2038 and wrap to 1901, breaking time comparisons and timers. C programs, 32-bit CPUs and libraries such as MySQL unix_timestamp returns zero still show the bug; a Boeing 787 generator fault after ~248 days demonstrates the same 32-bit tick overflow in embedded systems. Remediation is concrete: replace 32-bit timestamps with 64-bit timestamps, audit SQL/time functions and long‑running timers, and plan reboots or firmware updates for affected devices.
AI-written summary · about
chapters (5)
related talks
49mThe End of Time, 19 Years to Go
39mEverything Everywhere All at Once…in 2038
41mY2038 and Utmp/Wtmp on 64bit Systems
42mZettalinux: It's Not Too Late To Start
01h 26mDebug C++ Code - Best Time Travel Debugging Tech
50mTime Trial: Racing Towards Practical Timing Attacks
39mMitigating Integer Overflow in C
33mUndefined Behavior in C++: What Every Programmer Should Know and Fear