When amule crashes, it means it doesn't work like it should - so whatever happens to it's internal data it's undefined. It will, however,
attempt to save as match as it can, but no promises here - memory is already corrupted (otherwize it wouldn't crash on a first place).
Now, we don't want to have
another SIGSEG while saving data - so exception handler must be brief as possible: NO closing files/sockets/windows, NO freeing memory, NO calling destructors etc. Becouse all those make
access to internal datastructure which is corrupted somewhere.
Conclusion: when it crashes - come here to complain, post backtrace, curse developers. There's good chance that one of them will actually understand a problem and fix it
