Posted by Fernando Rodríguez on Feb 17, 2005; 5:02pm
URL: https://forum.world.st/Aaaaaaarrrggg-Broken-Image-tp3373131p3373139.html

>This is almost certainly recoverable. Here are a few things to try
(and in
>this order):

>1) Try a "panic" (the scream button on the system folder toolbar)
>2) Debugger allInstances do: [:each | each view destroy]
>3) Debugger allInstances do: [:each | Smalltalk developmentSystem
>removeEventsTriggeredFor: each]
>4) Open the Process Monitor, if any processes are listed as being in
state
>'debug', terminate them using the command on the context menu.


Unfortunately, I already created a new image with the 'fresh install'
option.
It was some misbehaving debugger view?

>image by mistake. Even if you do damage your image, the change log
records
>most of what you have done so you will be able to restore it at the
cost of
>some time. Ian Bartholomew's Chunk Browser tool is excellent for this
>purpose. To avoid having to fire up the Chunk Browser, you should:

>1) Ensure that all your work is packaged. Regularly save your
packages. I
>can't stress enough how important this is.

I just found that out. ;-)   When you modify a class that is a given
package
and save the image, is the package updated with the new version of the
class?

If not, is there a way to automate saving all user-defined packages?
Right now, I
only have 3 packages, so it's easy to remember saving them every now
and then,
but as soon as the number of packages increases...