I ended up fileouting what I could in headless mode (had utf8 issues for whatever reason so I didn't get it all), and rewriting the rest. :/ But what happens once will happen again... so some more generic solution for this would be nice.
Yuriy mentioned Oz, and it looks viable, provided it works with current pharo version and is capable of dealing with (most likely) corrupted memory. However as I personally prefer time traveling over archaeology, I would like having multiple snapshot of the image (10 minutes ago, 20 minutes ago) so if my image gets corrupted I loose at most 10 minutes of time. I can always dig it out, but there is always some work involved (downloading new image, setting it up, downloading work packages, digging out the old changeset, ...). On Tue, Jun 16, 2015 at 8:45 AM, Nicolai Hess <[email protected]> wrote: > > > Did you try to open (a copy of) the changes file with a new/fresh image? > Or you can use : > > ExternalChangesBrowser openOn:'FULLNAME_OF_OTHER_CHANGES_FILE' > to open a changes browser. > Good to know this is available now (I am still in Pharo 4 tho), but this is still archaeology for me. :) Anyway, I've resolved my current problem, so the question now is how to add some extra fault tolerance. Peter
