3 ms·

When dealing with physical systems it is impossible to have no bugs. To give an extreme example, there is a not a small chance that the cosmic rays can change a

When dealing with physical systems it is impossible to have no bugs. To give an extreme example, there is a not a small chance that the cosmic rays can change a bit in a system's memory - https://stackoverflow.com/questions/2580933/cosmic-rays-what-is-the-probability-they-will-affect-a-program https://stackoverflow.com/questions/2580933/cosmic-rays-what... The issue here is overflow due to time. The time is saved in a variable (don't know how much bits), which overflows after the gives period. Now there are two options 1. Upgrade circuits of every plane. These planes were designed/built a long time back. Bigger registers were not practical due to costs. 2. Document it and have a process for it.

pbhjpbhj 7y ago
Environmentally induced errors aren't software bugs, just because there's a problem elsewhere doesn't mean we shouldn't seek to mitigate other problems. In plane investigations I've looked at (not many) the issue has always been a compounding of several errors or shortcomings .. that strongly suggests you shouldn't let small errors build up in different systems, to me. [1] If it's a register which takes down the whole system then surely they'd know that (and could fix it with a watchdog that returned the effected systems to the boot state without reboot) -- other comments seem to be saying "meh, it's complex, doesn't matter what the error is as long as reboot fixes it"; that seems really dangerous in safety critical systems. [1] but I acknowledge the "better the devil you know" issue and that pragmatism and cost take over at some point.
viraptor 7y ago
> it is impossible to have no bugs. I agree with that. But once you know about a specific big, there is always a solution.