2 ms·
There are hard realtime systems for which segfaults are a game over, but even for the airplane, there will be a watchdog triggered and the system reboots. This
by aidenn0 9y ago
There are hard realtime systems for which segfaults are a game over, but even for the airplane, there will be a watchdog triggered and the system reboots. This means your control surfaces are neutral for about a second. There are some situations in which that could be fatal, but it typically is not.
If the system gets in a state where it is in a reboot loop, that is obviously bad, but those are more tractable to fix. In any event, I believe that FAA requires semi-formal analysis for software the failure of which would cause loss of life, but I might be wrong.
- nickpsecurity 9y agoHere's the regulations they usually go by: https://en.wikipedia.org/wiki/DO-178B https://en.wikipedia.org/wiki/DO-178B https://en.wikipedia.org/wiki/DO-178C https://en.wikipedia.org/wiki/DO-178C There's an ecosystem of products developed this way, products such as static analyzers to help develop them, and even companies assisting in any part of the lifecycle. Market shifted toward reusable components for things such as RTOS's and middleware. Examples include INTEGRITY-178B, LynxOS-178B, Alt's OpenGL + driver for Radeon, partitioning Ethernet/networking/filesystems, Esterel SCADE, SPARK Ada, and so on. Lots of good stuff came from this. On a tangent note, it's why I'm for software regulation where the useful subset of assurance methods that make those great become part of the requirements for commercial software. Defects will go down and predictability up across the board. Things will get more expensive with development slowing down a bit. That will probably be a good thing given Worse is Better effect market has been doing. I went into more detail on regulation prior results and some predicted ones here: https://www.schneier.com/blog/archives/2016/11/regulation_of_t.html#c6739118 https://www.schneier.com/blog/archives/2016/11/regulation_of...