Under "Ways to prevent" you suggest "Ways to prevent (by making them impossible)" and rewriting in JS or Rust, using smart pointers, etc.
This may prevent crashes in the narrow sense that it prevents SEGVs, etc. but it does not make runtime errors that lead to program shutdown impossible. To take an example, even if a C++ program only uses smart pointers, it is still possible to have null pointer dereferences, which then cause program shutdown. Runtime errors are also unrecoverable runtime errors are also possible JS/Rust. I don't disagree that safer languages eliminate a large class of crashes, but they don't make them impossible. -Ekr On Mon, May 23, 2016 at 9:56 PM, Nicholas Nethercote <n.netherc...@gmail.com > wrote: > Greetings, > > I've written a document called "All about crashes" which I've put on > the Project Uptime wiki: > > https://wiki.mozilla.org/Platform/Uptime#All_about_crashes > > It's about all the different ways we can discover, diagnose, and > address crashes. It's intended to be a comprehensive, because I want > to use it to help identify and prioritise all the ways we could do > better. > > I would appreciate any feedback people might have. I'm sure I have > gotten some things wrong, and omitted some things. Thanks in advance. > > Nick > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
