Re: Some example code for a new crash handler



Charles Iliya Krempeaux <tnt linux ca> writes: 
> Well, how about, instead of saving things over the original files,
> you save it as another file name.

You don't understand the problem - the problem is that once you get
the SEGV signal, any piece of memory in the program could contain
total junk. _Any_ piece. That means there is no way to do anything
sane. Say you save your spreadsheet - one of the values in the
100,000-row sheet could be slightly incorrect, for example.

Havoc



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]