3 ms·
Boeing didn't even test their 787 aircraft for integer overflows, and that's in a safety-critical environment, so I'm not sure I'd expect SSD vendors to be any
by mhandley 7y ago
Boeing didn't even test their 787 aircraft for integer overflows, and that's in a safety-critical environment, so I'm not sure I'd expect SSD vendors to be any better.
https://www.engadget.com/2015/05/01/boeing-787-dreamliner-software-bug/ https://www.engadget.com/2015/05/01/boeing-787-dreamliner-so...
Not that throwing an exception on integer overflow is any better, unless you catch the exception. The classic example here is the Ariane 5 failure:
http://sunnyday.mit.edu/accidents/Ariane5accidentreport.html http://sunnyday.mit.edu/accidents/Ariane5accidentreport.html
- everybodyknows 7y agoThe 787 case is most fascinating in that while the bug is dead simple, a fix is not. >Most importantly, the company's already working on an update that will patch the software vulnerability -- though there's no word on when its jets will receive it. My search of DDG turned up nothing about a resolution. Anyone know? I know what I would recommend, but marketing would not like it ;-)
- planteen 7y agoThis same problem also led to the loss of the Deep Impact spacecraft on its extended mission: "On September 20, 2013, NASA abandoned further attempts to contact the craft.[77] According to chief scientist A'Hearn,[78] the reason for the software malfunction was a Y2K-like problem. August 11, 2013, 00:38:49, was 232 tenth-seconds from January 1, 2000, leading to speculation that a system on the craft tracked time in one-tenth second increments since January 1, 2000, and stored it in an unsigned 32-bit integer, which then overflowed at this time, similar to the Year 2038 problem" https://en.wikipedia.org/wiki/Deep_Impact_(spacecraft)#Contact_lost_and_end_of_mission https://en.wikipedia.org/wiki/Deep_Impact_(spacecraft)#Conta...
- Tempest1981 7y agoYour superscript got eaten. 2^32