[Bf-committers] Save session recovery on SIGSEGV
desoto at blender.spaceisbig.com
Thu Feb 24 05:41:44 CET 2005
How about "joeedh.blend" just so we know who's fault it is ;) In all
seriousness.. I can't see this feature being very useful.. an aggressive
autosave setting with many versions seems smarter to me. Besides.. does
this even work on Windows? OSX? etc? /me does not know but would bet
not. I see the intent behind it, but how about this: Instead of coding
features that make crashes safer, lets code features that don't crash ;)
--Chris The Crash Test Dummy
Robert Wenzlaff (AB8TD) wrote:
> On Wednesday 23 February 2005 17:18, Alexander Ewering wrote:
>>>Hi. I've made a patch where BKE_undo_save_quit (the session recovery
>>>saving function) is called whenever a segmentation fault occurs.
>>>I don't know if this is a good idea, if it'll work cross platforms, or
>>>whatever, but anyway heres a patch.
>>Cool, I wouldn't have thought the state is sane enough still to save a file
>>in that situation
> There's a decent chance that you will save the item that made it SIGSEGV in
> the first place. It's usually an interaction with a tool, though, so would
> "probably" work most of the time. But you might want to make it save
> "crash.blend" instead of saving over quit.blend.
More information about the Bf-committers