[Lazarus] Playing with debuggers

Joost van der Sluis joost at cnoc.nl
Sun Oct 31 00:12:42 CEST 2021

Op 17-09-2021 om 21:19 schreef Joost van der Sluis via lazarus:
> Op 14-09-2021 om 17:12 schreef Martin Frb via lazarus:
>> On 14/09/2021 16:11, Joost van der Sluis via lazarus wrote:
>>>> 1)
>>>> All watches should be part of the "watches" list. (or alternative 
>>>> means must be found). This is so the debugger can update them, if 
>>>> the user changes memory (set a new value to a variable).
>>>> This is also helpful for the history window, and for "idle eval" (if 
>>>> the watches window is closed but the debugger is idle, then eval 
>>>> starts anyway).
>>> Yes, as you look carefully at the screencast, you'll see that the 
>>> history-option is removed. ;)
>> I am using the history a lot. So that needs to be fixed
> ;) I'll have to look into it, I never used it, really.
> But the next two weeks I'm on vacation, so it will have to wait.

Update: I've implemented watches and improved the list of threads and 
the callstack.

This discussion in mind myu first intention was to create some kind of 
global list with watches. But in the end I decided not to do something 
like that. After all, a 'watch' isn't something on it's own. There is a 
window that shows a few watches. So I made the list of watches part of 
the dialog.

Makes it also possible to show multiple dialogs with each it's own watches.

But only the history will get a challenge. But this also need some more 



More information about the lazarus mailing list