This is not so much about debugging; it's a much more general issue. Given that Smalltalk is designed to allow one to interact with objects, it always frustrates me when our many browsers hide their implementation. We should be able to open inspectors on the model and the UI instance quickly and easily. These would greatly facilitate learning how the browsers works and to be able to script things that the browser developer did not include.

e.g. How many methods am I looking at in this method browser?

e.g. I want to open a new method browser on a subset of the methods I am looking at. (The rewrite tool helps when the criteria are syntax-based, but ...)

and many more things.

From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Stephane Ducasse
Sent: March 9, 2017 03:37
To: Any question about pharo is welcome; Pharo Development List
Subject: [Pharo-users] What is the craziest bug you ever face

Hi guys

During the DSU workshop we were brainstorming about what are the most difficult bugs we faced and what are the conceptual tools that would have helped you.

Stef