Re:How Did Software Get So Reliable Without Proof? (1996) [pdf]
by seanwilson on Wednesday March 16, 2016 @01:55AM
(#11295331)
The paper is talking about rigorous formal mathematical proofs of correctness like in the sense of of the seL4 kernel (https://sel4.systems/Info/FAQ/) where they have confirmed the kernel is completely free of bugs such as buffer overflows, null pointer exceptions, use-after-free, etc.
[ Parent
| on HN ]
Re:How Did Software Get So Reliable Without Proof? (1996) [pdf]
by ktRolster on Wednesday March 16, 2016 @03:03AM
(#11295525)
Of course, there might be bugs in the specification (the proof the made was that the kernel matches the specification)
Re:How Did Software Get So Reliable Without Proof? (1996) [pdf]
by seanwilson on Wednesday March 16, 2016 @03:52AM
(#11295687)
> Of course, there might be bugs in the specification (the proof the made was that the kernel matches the specification)
Nothing is perfect, but this approach catches more bugs than any other technique. Also, some specifications are simple to specify e.g. it's not hard to specify that an array index must be within the bounds of the array and if you did get this wrong you'd notice quickly as you'd be unable to prove obvious facts are correct.