Hi Pete,
I had hoped we would have fixed most of these issues in the Squeak 6.0 release. Could you please confirm that you are not using an older version of Squeak?
As an adhoc measure, you could use the Do menu in the world main docking bar and choose "Close all debuggers", which sometimes works. It depends on whether new debuggers are appearing all the time (frequently invoking Close all debuggers a few up to a few dozens times might be successful), or whether exactly one debugger appears in the moment you close/abandon another debugger. In the latter case, manually terminating or destroying the process through the process browser might be worth a try.
In general, if you could share a screenshot of the debuggers plus your workspace code with us, there would be a chance to fix a bug in Squeak or to provide you with better assistance. :-)
Best, Christoph
________________________________ From: Beginners beginners-bounces@lists.squeakfoundation.org on behalf of crowd_struts_07@icloud.com crowd_struts_07@icloud.com Sent: Friday, December 2, 2022 1:15:10 AM To: beginners@lists.squeakfoundation.org beginners@lists.squeakfoundation.org Subject: [Newbies] Newbie question
Is there a way to stop the endless debugger windows when a process goes astray? I had code in a workspace which I tried to stop with CMD-. (Mac) which seemed to work most of the time but the last time it just created an unlimited number of debugger windows. I close them just to see more reappear. Besides writing better code :-) is there a way to stop the program and the endless debugger windows? Thank and apologies if this is something covered already.
Regards Pete _______________________________________________ Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners