problem gdb13.1 with lazarus2.2.6 Raspberry5/Debian12

[Fred vS]

Hello,
I initially used fpc deluxe, but not knowing how to uninstall a version, I preferred "apt-get install...".
After installing fcp3.2.3+lazarus4.0 arm64.deb, the gdb errors are the same.

Sorry, not sure to understand, so you are using the deb packages from debian server using "apt-get install..."?
And not the one from fpc sourceforge?

To uninstall fpcupdeluxe and install a new version, simply delete the directory /home/you/fpcupdeluxe and fpcup.ini, fpcupdeluxe.ini then reload the binary fpcupdeluxe to re-create a new version.

[Martin_fr]

Bug GDB with message "..ptype r.ftabmots..."
I think the problem appears depending on the type of variable being scanned (in this case, a dynamic array, etc.).

There aren't any settings for that.

GDB has a very very limited understanding of Pascal types. In order to get better results, years and years of work went into the IDE tweaking the input to GDB (e.g. appending ^ if necessary) in order to get as much info as possible.
But then in each GDB version different issue arose were GDB itself would crash.

I used to test with combination of more than 10 gdb versions versus 3 or 4 fpc versions and with different debug info settings.... Very time consuming.

Since a couple of years my focus moved to FpDebug (but that does only support i386/x86).
I still want to update the gdb backend of the IDE again. But I simply hadn't had time in a few years.

I had never gotten it 100% stable with the old gdb versions (can't workaround every gdb bug), and the newer gdb versions haven't always improved it.


As I said LLDB should work (and likely be more stable) on your platform.

IIRC the package is called LazDebuggerLLDB  (there MUST NOT be any "FP" in the name).
Well if you install it, install both: the one with and the one without "FP" in the name.

You can then test "LLDB alpha" and "LLDB+FpDebug" as debugger backends.

**IF** "LLDB+FpDebug" works, then great => that should give you a really good experience (though it be a a little bit slower showing watches)

Otherwise the "LLDB alpha" should work. (Use only "Dwarf 2"). However watches need to be entered C-style: obj->field


Unfortunately that are currently all the options.

[Fred vS]

Bug GDB with message "..ptype r.ftabmots..."
I think the problem appears depending on the type of variable being scanned (in this case, a dynamic array, etc.).

Could you give a demo program/code that produces that kind of message?

[Thaddy]

At least, build from source there aren't any issues I am aware of.

[Fred vS]

At least, build from source there aren't any issues I am aware of.

Same here, and if you dont want to touch to your system configuration, install it in your favorite custom folder:
 

Code: Pascal  [Select][+][-]

1.     $ ../configure --prefix=~/gdb-custom
2.     $ make
3.     $ make install

If you are not fan (like me) that GDB try to connect to the network, use --disable-debuginfod parameter in configure (Last Lazarus can deal to no download C debuginfo files but not to prevent gdb from connecting to the network).

Once you have the new GDB binary, also to not touch at your system, replace the old gdb in /fpcupdeluxe/fpcbootstrap/gdb/arm-linux/gdb  (that is a copy of /usr/bin/gdb in fact) with the new one.

And use fpc-Lazarus from /fpcupdeluxe/.

So all will be centralized in /fpcupdeluxe.