davidv1992 wrote:
I think a feature like this would be more useful if you could associate it with a specific breakpoint, both so you don't have to type it n times in a script, and also so that it is more useful when doing non-script-assisted debugging. Kind of like how the gdb cond command works. This also solves the problem that these expressions could get quite large if you have multiple breakpoints, and want some subset of them to have conditions.
Yes, this would be next step.
I am still thinking how to hack this into the debugger.
Probably I will have to remember condition as a string together with breakpoint and in case of breakpoint hit 'throw in' into parser the condition and see how it is resolved.
And ignore breakpoint hit if condition is false ...
But for now it is much more complicated for me so I added smth which was trivial to add and can have immediate added value