How Is Critical Life or Death Software Tested?

Re:How Is Critical Life or Death Software Tested? by z3t4 on Tuesday June 02, 2015 @01:52AM (#9644117)

One mistake that ppl do is they wrap their code around a try ... catch, where it's better to throw an error and exit. If there's an error in one place, chances are there are also errors elsewhere, so it's better to restart the program instead of continue with a bad state.

When the error gets thrown in your face, there's a higher chance that it gets fixed.

But this also have its setbacks. Loosing the whole state can be really bad.

[ Parent | on HN ]

Re:How Is Critical Life or Death Software Tested? by peteretep on Tuesday June 02, 2015 @03:43AM (#9644461)

I'm really note sure why you think catching an error in a separate process is somehow superior to catching it in a higher scope

[ Parent | on HN ]

Re:How Is Critical Life or Death Software Tested? by sacado2 on Tuesday June 02, 2015 @10:40AM (#9646134)

I think it depends on the kind of error. If it is a "bug-detected" error (null-pointer dereference, out-of-bounds, divide-by-zero, out-of-memory, etc.), you better restart the program since you're in an unstable state. If it is a "domain-specific" error (connection lost, robot could not reach its destination, battery low, etc.), you better deal with it as soon as possible.

[ Parent | on HN ]