Well, I could give you a special debug executable that can dump core*, but I'm not sure how useful it'd be. From what you describe, it sounds like the freeze messed up some of your files. ext3 reduces the chance of such things happening, but it doesn't eliminate the possibility entirely. Usually such corruption only happens to files that were written at the time of the crash (so, most likely the DROD dat files ..), but depending on what the filesystem were doing it's possible that other files were corrupted.
So, we don't know what went wrong. Now, DROD should of course not segfault, but depending on what the corruption is, this might be something that couldn't happen at all otherwise. In this kind of situation I think it's better to try a reinstall first, so I don't go looking for bugs that might not actually exist.
Before you do a reinstall, back up your dats. They're either located in ~/.caravel/drod-2_0 (per-user data option), or in the Data subdir where you installed DROD (shared data option). There will always be .dat files in the latter place, but if you used the per-user option they won't be updated. If you're not sure, the files are probably in ~/.caravel/drod-2_0, but if you want to be certain, you can check ~/.caravel/drod-2_0/DataPath.txt. The
first path is the location of the data. Anyway, once you've found the .dats, copy all of them somewhere safe. Then do a reinstall.
After the reinstall, if the .dats were in ~/.caravel/drod-2_0, you don't have to do anything. DROD will automatically use your existing dats. (Otherwise, of course, copy your old dats back to where they were before). With some luck that'll fix your problems! Let me know what happens
- Gerry
* Basically, in stead of having SDL open parachutes for a smooth landing and disappearing in a puff of smoke, we fire DROD firmly into the ground so we can have a look at the scattered debris.
