[squeak-dev] Corrupted sources file = big trouble

Max Leske maxleske at gmail.com
Fri Mar 15 11:28:26 UTC 2013


If you try Tanker, let me know how that worked for you.


On 15.03.2013, at 11:32, Frank Shearar <frank.shearar at gmail.com> wrote:

> I'm happy to give it a try; I'd like to see Tanker running in Squeak
> anyway. If it uses Monticello it might not work though. But if it
> serialised the actual CompiledMethods and such it might just work.
> 
> frank
> 
> On 15 March 2013 10:21, Max Leske <maxleske at gmail.com> wrote:
>> Would Tanker be an option? http://rmod.lille.inria.fr/web/pier/software/Tanker
>> 
>> 
>> On 15.03.2013, at 11:10, Frank Shearar <frank.shearar at gmail.com> wrote:
>> 
>>> So I freely confess: I should not have deleted the directory from
>>> which I was running an image. When I saved the image, the image still
>>> worked, but of course its changes file was broken.
>>> 
>>> I now have a few tens of hours of work in an image that I need to
>>> extract only the following techniques all fail:
>>> * filing out the class
>>> * making a new changeset and filing that out
>>> * saving the package through MC
>>> * deleting the corrupted changes file
>>> 
>>> So one option that I don't particularly want to do is to open a new
>>> image and hand cut-n-paste (via emacs, because on Linux the line
>>> endings get messed up copying between Squeak images directly), method
>>> by method, the source.
>>> 
>>> Is there an easier way of recovering from this mess?
>>> 
>>> frank
>>> 
>> 
>> 
> 



More information about the Squeak-dev mailing list