On 09/09/2016 09:42, Graeme Geldenhuys wrote:
On 2016-09-08 19:07, Martin Frb wrote:
And you need to press the "current" button in the stack. doubleclick
does not select it.
Ah, that was the problem. Thanks for help. Amazing I never noticed it
before.
A question though:
Why must you click "current" before the stack (an local variables)
update? Wouldn't that be the obvious thing to do (desired behaviour)
when you double click back into the stack history? The "current" button
just seems redundant.
No idea why, but iirc it always was like this. (that applies to
breakpoints too)
double click => jump to code
current => set the frame for inspection
Years ago the debugger would get all watches before it could do any
further action, if "current" was changed (and with many watches this
could be very slow). So if you would double click, several frames, to
find the one you are interested, you would have a lot of waiting time.
Now the debugger, can continue even if there are still watches to
inspect, so it would be faster.
Maybe double click can (optionally?) include "current".
------------------------
Not sure, if in case of exception the correct frame is selected (ideally
not the one in fpc_except).
This is sometimes one frame off, because some methods in RTL have no
stackframe.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus-ide.org/listinfo/lazarus
