Re:Setting the clock ahead to see what breaks
by nickweb on Tuesday January 24, 2023 @03:28AM
(#34500999)
I’m curious as a hobby programmer - how would these issues be rectified? Hope that the source code is available to add in new defines for 64bit time? Patch existing libraries after stracing existing programs without source code? Might need to take a deep dive into C for 2038!
[ Parent
| on HN ]
Re:Setting the clock ahead to see what breaks
by pushedx on Tuesday January 24, 2023 @04:42AM
(#34501597)
For reference, strace is a Linux facility that wouldn’t be present on a bare-metal embedded application of C, or other operating system.
Re:Setting the clock ahead to see what breaks
by danuker on Tuesday January 24, 2023 @07:30AM
(#34502762)
I suspect you can run strace in a dev environment, iron out the bugs, then deploy the new embedded app.
Re:Setting the clock ahead to see what breaks
by comfydragon on Tuesday January 24, 2023 @10:47PM
(#34514171)
Assuming you have an ability to run your whole bare-metal application in a simulated/"dev" environment. Not everyone has that luxury. That becomes much easier if the micro you're targeting has support of some kind in say QEMU, but those are fairly few and far between.
Re:Setting the clock ahead to see what breaks
by tetha on Tuesday January 24, 2023 @05:03PM
(#34511178)
Put the system into single user mode 15 minutes before disaster. Update all filesystem times and the HW clock to 0 offline. Reboot a couple of times 30 minutes later and fix the timediff in APIs surrounding the system. Easy going.
I think I have been in too many horrible workarounds over the last couple of weeks.