1/0 = 0 - Hackdot

Re:1/0 = 0 by WalterBright on Saturday August 11, 2018 @04:46PM (#17741428)

Aircraft and spacecraft all have backup systems for critical software. When software self detects a bug (such as an assert failure) the offending computer is shut down and electrically isolated, and the backup is engaged.

What is absolutely NOT done is soldiering on with a computer in an unknown state.

Any software system that is life critical is either designed this way or is very badly engineered. I've written a couple articles about this:

https://www.digitalmars.com/articles/b39.html https://www.digitalmars.com/articles/b40.html

[ Parent | on HN ]

Re:1/0 = 0 by karmakaze on Monday August 13, 2018 @09:46AM (#17750000)

And what if the program is the lowest level and getting into an impossible state due to a hardware issue (bad bit). At some level a program has to soldier-on.

[ Parent | on HN ]

Re:1/0 = 0 by WalterBright on Monday August 13, 2018 @05:28PM (#17753767)

Then it sets an I/O pin that pulls the reset switch.

[ Parent | on HN ]

Re:1/0 = 0 by karmakaze on Tuesday August 14, 2018 @08:25AM (#17757227)

I cant tell ic you're being serious. The appropriateness of that would depend on whether the hardware condition was persistent in which case we have a reboot loop. It doesn't seem resonable for software meant to run in a harsh envirinment to assume prefect rumtime conditions. Do probabilitites and tradeoffs ever get considered when faced with inconsistent state?

[ Parent | on HN ]