Hi Pete,

A few things. If you had a cascade of debuggers it is very difficult to stop them. You need to stop the process that is generating them. There are a few ways to do that. To halt the current process press Alt + . (press and hold alt key then period)

This is highly likely to get your process but it may not. If it looks like your process you are good to go. You can try a few times and you might get lucky. (press proceed if it is not your process).

Since you are able to interact with the system on the World menu select: open > process browser. You can find your process and then right click on it and select debug.

Also your code is safe. It is in your changes file. From the World menu select: changes > recently logged changes ... and you will find your code. This works even if you kill your image (as long as you don't replace the changes file).

Hope that helps!

Ron Teitelbaum

On Fri, Dec 2, 2022 at 12:16 AM P Padilcdx ppadilcdx@gmail.com wrote:

Hi Christoph

I am using the 6.0 release. I was using a recursive algorithm. I did use the menu to close all the debuggers but more kept coming. I might have given up too early and force-quit Squeak. Just wondered if there was another magic trick. Thank you for the prompt reply!

PS. Code was not saved due to the force-quit. But it was writing to the Transcript and from what I could deduce, that was the reason for the unlimited debugger windows with a “didNotUnderstand” at the top of the frames. Hope that makes sense.

Regards Pete _______________________________________________ Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners