[Pharo-dev] [QA] Debugger buttons explained

Stephane Ducasse stepharo.self at gmail.com
Wed Feb 8 10:17:13 EST 2017


looks good to me.

On Tue, Feb 7, 2017 at 8:40 AM, Sven Van Caekenberghe <sven at stfx.eu> wrote:

>
> > On 7 Feb 2017, at 08:05, Stephane Ducasse <stepharo.self at gmail.com>
> wrote:
> >
> > Sven I do not get
> >
> > Step over the highlighted message, i.e. do not follow the sent message,
> taking debugger control after the method invoked returns or whenever
> execution should return inside a block used as an argument before that.
> >
> > in particular the taking debugger control
> > may be
> >
> > give back debugger control?
>
> Give back might be clearer than take back, I guess, I don't know.
>
> Maybe the 'before that' should be moved too, as in
>
> Step over the highlighted message, i.e. do not follow the sent message,
> give back debugger control after the method invoked returns or whenever
> before that execution should return inside a block used as an argument.
>
> > On Mon, Feb 6, 2017 at 7:39 PM, Sven Van Caekenberghe <sven at stfx.eu>
> wrote:
> >
> > > On 6 Feb 2017, at 18:55, Hilaire <hilaire at drgeo.eu> wrote:
> > >
> > > How will you describe these buttons in the debugger?
> > > Here are proposals for tooltips, please fix it, I am sure there are
> > > better way to write it.
> > >
> > > Proceed
> > > Quit the debugger and resume the execution of the method.
> > >
> > > Restart
> > > Reset the local variable and restart stepping at the beginning of the
> > > method.
> > >
> > > Into
> > > Step in the highlighted message, i.e. follow the sent message in its
> method.
> > >
> > > Over
> > > Execute the highlighted message, i.e. do not follow the sent message in
> > > its method.
> > >
> > > Through
> > > Execute the highlighted message, when argument is a bloc to #do:,
> > > #collect:, #select: #detect: step in the bloc.
> >
> > That last one is not correct. It has nothing to do with specific
> iteration selectors. It means: stop when execution returns in one of the
> argument blocks. It also works for #on:error: #streamContents: or any other
> message that accepts blocks as argument - which is pretty cool.
> >
> > Consult DebugSession for good descriptions of the actions.
> >
> >
> > This is my version/take, probably not perfect either.
> >
> >
> > Into
> >
> > Step in the highlighted message, i.e. follow the sent message, taking
> debugger control in the method invoked.
> >
> > Over
> >
> > Step over the highlighted message, i.e. do not follow the sent message,
> taking debugger control after the method invoked returns.
> >
> > Through
> >
> > Step over the highlighted message, i.e. do not follow the sent message,
> taking debugger control after the method invoked returns or whenever
> execution should return inside a block used as an argument before that.
> >
> > Restart
> >
> > Go back the start of the current execution context, resetting all local
> variables and take debugger control.
> >
> > Continue
> >
> > Relinquish debugger control and proceed execution from the current point
> of debugger control.
> >
> >
> > > https://pharo.fogbugz.com/f/cases/19654/Tooltips-with-
> description-of-the-over-and-through-debugger-buttons-actions
> > >
> > > --
> > > Dr. Geo
> > > http://drgeo.eu
> > >
> > >
> >
> >
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20170208/80edeea6/attachment.html>


More information about the Pharo-dev mailing list