FpDebug feature request
lazarus / 12-Debugger

----------------------------------------------------------------------
440bx · 2024-10-02 21:54

Hello,

Case 1:

When hovering over an array variable, if the array is part of a record
that is being accessed in the scope of a "with" statement then FpDebug
cannot currently show the value of the referenced array element. 
Please see the first attachment.

Case 2:

if the array variable is explicitly qualified with the record name
then FpDebug _can_ (and does) show the value of the referenced array
element.  Please see the second attachment.

the feature request is: add the capability in FpDebug to resolve the
scope in which the variable appears (it normally does anyway.) This
would enable it to show the value in case 1 as it does in case 2.

Comments welcome.

----------------------------------------------------------------------
Martin_fr · 2024-10-02 23:17

There is no "with" info in the debug info. (dwarf has it, fpc does not
use it / fpdebug hence doesn't have it yet either).

IIRC, some variables work in "with" blocks, because codetools gets a
go at it first. (but I may be mistaken).

If I am not mistaken, then it needs to be dealt with in codetools.
(i.e. not something I (usually) work on / but something that can be
done...)

----------------------------------------------------------------------
Martin_fr · 2024-10-02 23:19

Just tested, codetools resolves this in other cases...

So bug report against code tools...

----------------------------------------------------------------------
440bx · 2024-10-02 23:29

Quote from: Martin_fr on October 03, 2024, 01:17:36 amThere is no
"with" info in the debug info. (dwarf has it, fpc does not use it /
fpdebug hence doesn't have it yet either).I see.  Without that
information it's definitely complicated to say the least.

Quote from: Martin_fr on October 03, 2024, 01:17:36 amIIRC, some
variables work in "with" blocks, because codetools gets a go at it
first. (but I may be mistaken).
That would explain why there are cases in which it works.

Quote from: Martin_fr on October 03, 2024, 01:17:36 amIf I am not
mistaken, then it needs to be dealt with in codetools. (i.e. not
something I (usually) work on / but something that can be done...)
It would be nice but, I think the real solution is to have FPC emit
the necessary debug info. 

talking about info... thank you for all that information.