News for hackers. Stuff that matters.
Re:Are we shooting ourselves in the foot with stack overflows? by outworlder on Tuesday February 18, 2014 @08:15AM (#7257927)
Yes, it is an option. It should fail as fast as possible, that's why you have contingencies in place. For instance, the Space Shuttle's computers checked their results against one another. If a discrepancy was detected, the computer would be immediately voted out. In case all computers were compromised, there was yet another computer with different hardware and software.

The point is that any erroneous result would cause the offending computer to be voted out immediately. And that's what you want, otherwise the system will appear to work fine, while being in an undefined state.

Re:Are we shooting ourselves in the foot with stack overflows? by simpleigh on Tuesday February 18, 2014 @08:28AM (#7257981)
It is an option, but not always the best option.

I think it was one of the Mars landers where they disabled error detection for landing. If the system reset near the ground then the lander would crash before the controller had rebooted, whereas a small error might not have disrupted the landing at all.

Fail fast is good advice, but should be weighed against other strategies to choose the most appropriate one for the circumstance.