Feb. 6, 2012
1:48 p.m.
In the latest Pharo Release we pushed a new Setting for the Debugger: see Settings / Debugging / Filter out common message sends, when enabled the Debugger behaves a bit nicer in most cases by filtering some non-interesting contexts: - "self halt" will now open the Debugger in the sender context, not somewhere on Halt / Object - sends to Kernel Classes are not shown (like Dictionary >> #at:ifAbsent: #do: #collect: ...) - a failing TestCase will open the Debugger in the test method itself So all in all it will save you some clicks and concentrate on the important stack elements For those interested in the details or wanting to extend it see Debugger >> #shouldDisplayContext: best cami