Inspect variable with gdb unparsed remainder problem
lazarus / 12-Debugger

----------------------------------------------------------------------
Dmitriy · 2021-10-26 10:32

I can not inspect string variable.
Debugger says ###("gdb unparsed remainder:...)###
(like on screenshot)
How to inspect this variable in IDE (Lazarus 2.0.12)?
Best regards, Dmitriy

----------------------------------------------------------------------
Martin_fr · 2021-10-27 13:41

If you are on Win/Linux, 2.0.12 already includes fpdebug. You may need
to install the package LazDebuggerFp.

Otherwise, I am not sure how much code the IDE already have to try and
work around that. You may report it as a bug, if you can reproduce it.
I can't tell it it is fixable at all, or when.

You can also try to download a diff version of gdb from our
sourceforge page. But I do not expect it to make a difference.

----------------------------------------------------------------------
MarkMLl · 2021-10-27 14:06

I meant to confirm this and comment yesterday evening: it only affect
the local variables window, not the dropdown value when you hover over
a variable in the source window.

MarkMLl

----------------------------------------------------------------------
Martin_fr · 2021-10-27 14:34

The local Window currently shows more or less pure gdb replies.

So yes its quality is lower. Getting the improved results, would cause
a bit of slowdown (especially if there are lots of locals). So best is
to add any value like this to the watches.

----------------------------------------------------------------------
MarkMLl · 2021-10-27 14:49

The local window truncates it, but the dropdown doesn't.

Can this at least be made configurable?

MarkMLl

----------------------------------------------------------------------
Martin_fr · 2021-10-27 15:02

In principal, it can be configurable. But it needs quite some work on
the gdbmi debugger backend.

It also depends, what will happen to the frontend. There is some todo
there... Joost was working on some interesting stuff in his DAB. If
that gets ported, that may offer better options for this here issue
to.

It is not just changing one or two commands to gdb.

At the moment the IDE gets all locals in a single gdb output.
To change it, the gdb backend would have to
- get the names
- create dummy watches for each
- eval them each
- collect, and then send the result.

That also means, that other than the watches win that gradually fills,
the locals would be empty, till all locals are there.

Of course clever tricks, like spotting integers and keep them could be
done.... But that is more code to implement to get it done.