The Debugger bugs me

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

The Debugger bugs me

Tobias Pape
Hey,

using the current trunk (doest not happen in 4.5), I cannot use the
debugger in a useful way anymore.
  Regardless of what I do in the editor view of the Debugger, after
a second or so, I tries to select the current expression (as if I had
clicked 'Where')[1] and scrolls to that place. This is especially annoying
when scrolling around long methods or trying to do a printIt or exploreIt
on other expressions…

Any clue?

Best
        -Tobias


[1]: I also have the impresison that, when one uses 'toggle break on entry', that
    the current expression is off-by-one with the actually current one.
Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

Tobias Pape

On 07.03.2015, at 00:17, Tobias Pape <[hidden email]> wrote:

> Hey,
>
> using the current trunk (doest not happen in 4.5), I cannot use the
> debugger in a useful way anymore.
>  Regardless of what I do in the editor view of the Debugger, after
> a second or so, I tries to select the current expression (as if I had
> clicked 'Where')[1] and scrolls to that place. This is especially annoying
> when scrolling around long methods or trying to do a printIt or exploreIt
> on other expressions…
>
> Any clue?
>
> Best
> -Tobias
>
>
> [1]: I also have the impresison that, when one uses 'toggle break on entry', that
>    the current expression is off-by-one with the actually current one.

Addendum: seems _only_ to happen with 'toggle break on entry' methods, that actually
   lose their formatting and seem "pretty"-printed. Can anyone confirm?
Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

timrowledge
In reply to this post by Tobias Pape
I know we’ve seen this before at least once but can’t recall any more detail. It’s not a new thing, or at least not a totally new thing.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
"How many Kzin does it take to change a lightbulb?”
"None. You can scream and leap in the dark."




Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

Chris Muller-3
In reply to this post by Tobias Pape
On Fri, Mar 6, 2015 at 5:17 PM, Tobias Pape <[hidden email]> wrote:
> Hey,
>
> using the current trunk (doest not happen in 4.5), I cannot use the
> debugger in a useful way anymore.
>   Regardless of what I do in the editor view of the Debugger, after
> a second or so, I tries to select the current expression (as if I had
> clicked 'Where')[1] and scrolls to that place. This is especially annoying
> when scrolling around long methods or trying to do a printIt or exploreIt
> on other expressions…

This issue definitely exists in 4.5 and yes, it is annoying.  I
believe if you can make the editor dirty (e.g., insert whitespace
somewhere), that you'll be able to stop it so you can look at the
method.

> Any clue?

I *think* this is related to a change Frank did a couple of years ago
where it was desired to fix updating the method in the debugger,
pressing Command+S [Accept] and having the new code be reflected
rather than the old..

> Best
>         -Tobias
>
>
> [1]: I also have the impresison that, when one uses 'toggle break on entry', that
>     the current expression is off-by-one with the actually current one.

Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

Frank Shearar-3
On 8 March 2015 at 18:16, Chris Muller <[hidden email]> wrote:

> On Fri, Mar 6, 2015 at 5:17 PM, Tobias Pape <[hidden email]> wrote:
>> Hey,
>>
>> using the current trunk (doest not happen in 4.5), I cannot use the
>> debugger in a useful way anymore.
>>   Regardless of what I do in the editor view of the Debugger, after
>> a second or so, I tries to select the current expression (as if I had
>> clicked 'Where')[1] and scrolls to that place. This is especially annoying
>> when scrolling around long methods or trying to do a printIt or exploreIt
>> on other expressions…
>
> This issue definitely exists in 4.5 and yes, it is annoying.  I
> believe if you can make the editor dirty (e.g., insert whitespace
> somewhere), that you'll be able to stop it so you can look at the
> method.
>
>> Any clue?
>
> I *think* this is related to a change Frank did a couple of years ago
> where it was desired to fix updating the method in the debugger,
> pressing Command+S [Accept] and having the new code be reflected
> rather than the old..

It could be, but I remember back then the debugger kind've oscillating
between two selections, and I _think_ my change helped mitigate that.
But I certainly did monkey around with the Debugger, so might well be
implicated :)

frank

>> Best
>>         -Tobias
>>
>>
>> [1]: I also have the impresison that, when one uses 'toggle break on entry', that
>>     the current expression is off-by-one with the actually current one.
>

Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

marcel.taeumel (old)
In reply to this post by Tobias Pape
Cannot reproduce the bug. Can you give some specific steps to get it?

Best,
Marcel
Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

Chris Muller-4
In reply to this post by Frank Shearar-3
On Tue, Mar 10, 2015 at 3:00 AM, Frank Shearar <[hidden email]> wrote:

> On 8 March 2015 at 18:16, Chris Muller <[hidden email]> wrote:
>> On Fri, Mar 6, 2015 at 5:17 PM, Tobias Pape <[hidden email]> wrote:
>>> Hey,
>>>
>>> using the current trunk (doest not happen in 4.5), I cannot use the
>>> debugger in a useful way anymore.
>>>   Regardless of what I do in the editor view of the Debugger, after
>>> a second or so, I tries to select the current expression (as if I had
>>> clicked 'Where')[1] and scrolls to that place. This is especially annoying
>>> when scrolling around long methods or trying to do a printIt or exploreIt
>>> on other expressions…
>>
>> This issue definitely exists in 4.5 and yes, it is annoying.  I
>> believe if you can make the editor dirty (e.g., insert whitespace
>> somewhere), that you'll be able to stop it so you can look at the
>> method.
>>
>>> Any clue?
>>
>> I *think* this is related to a change Frank did a couple of years ago
>> where it was desired to fix updating the method in the debugger,
>> pressing Command+S [Accept] and having the new code be reflected
>> rather than the old..
>
> It could be, but I remember back then the debugger kind've oscillating
> between two selections, and I _think_ my change helped mitigate that.
> But I certainly did monkey around with the Debugger, so might well be
> implicated :)

Yeah, your fix made it better than it was, I only said "Frank" to try
to help zero-in on the cause so we can fix it the rest of the way.
:)

Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

Chris Muller-3
In reply to this post by marcel.taeumel (old)
> Cannot reproduce the bug. Can you give some specific steps to get it?

I believe if you halt in a method, then change that method in
*another* browser, so that the one in the debugger is the old version,
the code pane in the debugger is now on a "refresh" loop such that the
user cannot stay scrolled where they want nor select other text and
have it stay selected..

> Best,
> Marcel
>
>
>
> --
> View this message in context: http://forum.world.st/The-Debugger-bugs-me-tp4810142p4810949.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>

Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

Tobias Pape

On 10.03.2015, at 18:19, Chris Muller <[hidden email]> wrote:

>> Cannot reproduce the bug. Can you give some specific steps to get it?
>
> I believe if you halt in a method, then change that method in
> *another* browser, so that the one in the debugger is the old version,
> the code pane in the debugger is now on a "refresh" loop such that the
> user cannot stay scrolled where they want nor select other text and
> have it stay selected..

Ohhh yes, that was my scenario.
I more and more use "toggle break on entry" to provoke a debugger
and immediately after disable the break… I shouldn't probably.
but then again, the pretty-printed code is not that pretty actually.
but that's another discussion :)

best
        -tobias


Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

marcel.taeumel (old)
Reply | Threaded
Open this post in threaded view
|

Re: The Debugger bugs me

Tobias Pape
\o/
 |
/ \


On 11.03.2015, at 05:44, Marcel Taeumel <[hidden email]> wrote:

> Fixed: http://forum.world.st/The-Trunk-Tools-mt-550-mcz-td4811137.html
>
> Best,
> Marcel