Pharo 6.1 debugger - suggestions break once, does funny things?
While Iâm on a debugger trip⦠anyone else also notice that the Suggestions, Break once debug option acts weirdly? I seem to get a debugger but it halts several lines after where I have said, and if I start stepping the debugger seems to jump to funny places and show values that donât line up with what I know is happening? If I use Suggestions, Break it seems to work correctly (apart from the Step Through I mentioned in another thread). Tim
2017-09-11 1:26 GMT+02:00 Tim Mackinnon <tim@testit.works>:
While Iâm on a debugger trip⦠anyone else also notice that the Suggestions, Break once debug option acts weirdly? I seem to get a debugger but it halts several lines after where I have said, and if I start stepping the debugger seems to jump to funny places and show values that donât line up with what I know is happening? If I use Suggestions, Break it seems to work correctly (apart from the Step Through I mentioned in another thread).
Tim
Thats because the "Break once" creates a MetaLink that when executing this Metalink it removes itself from the methode prior to the break-command. If now the debugger opens the method, it executes a context to a method that already had changed. (the actual method bytecode only exists in the current context). You can see the "real" bytecode of the contexts method if you select GTs bytecode view.
That makes sense - but in a practical usability sense its broken - it doesnât give me a useful breakpoint to step through code where I expect. Should I raise a Fogbugz for this? Or should we just remove this feature if we canât do it right? Tim
On 12 Sep 2017, at 11:09, Nicolai Hess <nicolaihess@gmail.com> wrote:
2017-09-11 1:26 GMT+02:00 Tim Mackinnon <tim@testit.works <mailto:tim@testit.works>>: While Iâm on a debugger trip⦠anyone else also notice that the Suggestions, Break once debug option acts weirdly? I seem to get a debugger but it halts several lines after where I have said, and if I start stepping the debugger seems to jump to funny places and show values that donât line up with what I know is happening? If I use Suggestions, Break it seems to work correctly (apart from the Step Through I mentioned in another thread).
Tim
Thats because the "Break once" creates a MetaLink that when executing this Metalink it removes itself from the methode prior to the break-command. If now the debugger opens the method, it executes a context to a method that already had changed. (the actual method bytecode only exists in the current context).
You can see the "real" bytecode of the contexts method if you select GTs bytecode view.
On 12 Sep 2017, at 12:44, Tim Mackinnon <tim@testit.works> wrote:
That makes sense - but in a practical usability sense its broken - it doesnât give me a useful breakpoint to step through code where I expect. Should I raise a Fogbugz for this?
Yes, please add an issue. I wanted to see if I can improve the debugger for this⦠Marcus
participants (3)
-
Marcus Denker -
Nicolai Hess -
Tim Mackinnon