Corrupted database after crashing on save about scratchabit HOT 5 CLOSED

I triggered the crash again, got a screen capture this time:
http://projectgus.com/misc/esp8266/scratchabit_crashonsave.png

Looks like self.func_end[addr] is of type Function, but engine.py:478 expects a number?

from scratchabit.

First of all, code makes a backup of previous files before saving new versions, so hope you didn't lose anything!

(And another good reason to have git integration ;-) ).

from scratchabit.

Should be fixed in 50a4311 . But Angus, if you use SAB in "production", do let me know, because otherwise I assume noone does, and I can do an breaking changes without thinking much. And if you use it like that (why not set up public project for it?), the best suggestion I'd have is to use the latest tagged version, currently 0.6. I'm working on robust function detection for 0.7. New YAML-based format for 0.8. And sadly, I don't explicitly have transparent database migration path on roadmap. So, if you expect something like that, let me know, and I'd still need help with that (or, you'd need my hints on how to migrate DB to new version).

from scratchabit.

Thanks Paul, appreciate the quick response!

I'm only doing fairly quick/simple bits of investigation on individual object files at the moment, so I'm not dependent on the database staying stable. Happy to live on the "bleeding edge" for now as things develop.

from scratchabit.

Sounds good, thanks for confirming, that's pretty much how I use it too so far, while pumping up features ;-).

from scratchabit.