[Pharo-project] Fancier Debugger
Hi everyone, last friday I spent some 20mins on improving the debugging experience (at least for me) by doing to following: - removed many "core" message sends from the context stack in the debugger - automatically expand the context stack if the last stackframe is selected For the first task I added a method which filters out all message sends which IMO are mostly uninteresting when debugging (right now still a but dirty implemented..): - #ifTrue: #ifFalse.... and so forth - iteration internals on Collections: #do: - Message sends to Blocks / MethodContexts: #on:do: #value: ... - Basic accessors on dicts: #at: #at:put: .... at least for me this helps me incredibly with locating important pieces of code in the debugger e.g. reducing the noise.. So is there any interest in this to be added? (of course with a settings switch to turn it on/off... in case you work on the filtered messages) If so I will implement it a bit cleaner and add a decent settings entry... cami
I'd use it :) 2011/7/18 Camillo Bruni <camillo.bruni@inria.fr>
Hi everyone,
last friday I spent some 20mins on improving the debugging experience (at least for me) by doing to following:
- removed many "core" message sends from the context stack in the debugger - automatically expand the context stack if the last stackframe is selected
For the first task I added a method which filters out all message sends which IMO are mostly uninteresting when debugging (right now still a but dirty implemented..):
- #ifTrue: #ifFalse.... and so forth - iteration internals on Collections: #do: - Message sends to Blocks / MethodContexts: #on:do: #value: ... - Basic accessors on dicts: #at: #at:put: ....
at least for me this helps me incredibly with locating important pieces of code in the debugger e.g. reducing the noise..
So is there any interest in this to be added? (of course with a settings switch to turn it on/off... in case you work on the filtered messages)
If so I will implement it a bit cleaner and add a decent settings entry...
cami
-- Bernat Romagosa.
Dear Camillo, On Mon, Jul 18, 2011 at 12:56 AM, Camillo Bruni <camillo.bruni@inria.fr> wrote:
So is there any interest in this to be added? (of course with a settings switch to turn it on/off... in case you work on the filtered messages)
that would be an awesome addition, please have it integrated. Also, if you have some expertise in the debugger, Doru would certainly appreciate some help in separating the model from the UI code. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
You should show us a demo :) Any improvement is welcome. On Jul 18, 2011, at 12:56 AM, Camillo Bruni wrote:
Hi everyone,
last friday I spent some 20mins on improving the debugging experience (at least for me) by doing to following:
- removed many "core" message sends from the context stack in the debugger - automatically expand the context stack if the last stackframe is selected
For the first task I added a method which filters out all message sends which IMO are mostly uninteresting when debugging (right now still a but dirty implemented..):
- #ifTrue: #ifFalse.... and so forth - iteration internals on Collections: #do: - Message sends to Blocks / MethodContexts: #on:do: #value: ... - Basic accessors on dicts: #at: #at:put: ....
at least for me this helps me incredibly with locating important pieces of code in the debugger e.g. reducing the noise..
So is there any interest in this to be added? (of course with a settings switch to turn it on/off... in case you work on the filtered messages)
If so I will implement it a bit cleaner and add a decent settings entry...
cami
participants (4)
-
Bernat Romagosa -
Camillo Bruni -
Damien Cassou -
Stéphane Ducasse