I've worked on an app that did demand-based dynamic loading of memory using the segfault handler. So there are definitely uses for this, they just aren't common.
Sent from my iPhone On Oct 17, 2011, at 10:21 AM, Norbert Nemec <norb...@nemec-online.de> wrote: > On 17.10.2011 14:54, Steven Schveighoffer wrote: >> Your best bet is to close the application, and possibly print a stack >> trace. Trying to continue is like continuing to drive when you get a >> flat tire. You are just going to keep damaging your car! > > To stick with this nice analogy: > > Trying to recover fully from a segfault is indeed like continuing to ride > with a flat tire. Bad idea! > > Accepting the system default segfault handling is like abandoning the whole > valuable truckload just because of a flat tire. Not such a good idea either. > > Sure, an emergency save may fail because of the memory corruption, but there > is a very good chance that it still works because the essential data > structures happen to be unaffected.
