Preparing FPC 3.2.4, point out road blocks now

[Alexx2000]

Hello,
I do not agree with you @Alexx2000.

Hi,
What you suggest, wait forever? If someone build a binary package later then it can be uploaded later, I don't see a problem here.

[BSaidus]

Hello,
I do not agree with you @Alexx2000.

Hi,
What you suggest, wait forever? If someone build a binary package later then it can be uploaded later, I don't see a problem here.

Hi Alexx2000, I think I maybe a dis-synchronization in this situation. Imaging someone building package later with some fixes the the Release ones do not contains.

[Wings2018]

Hello team,

As I'm currently facing GDB-problems using FPC 3.2.2 (GDB v7.2) I wonder which GDB-version will get linked to the upcoming FPC 3.2.4? I noticed GDB v16.2 is the most recent one, but CoPilot also told me a GDB v11.x or v12.x might be better to link to FPC.

Am I too late to request a more recent GDB-version to be linked to FPC 3.2.4? Of course, not sure if it will solve my problems, but better safe than sorry

[440bx]

As I'm currently facing GDB-problems using FPC 3.2.2 (GDB v7.2) I wonder which GDB-version will get linked to the upcoming FPC 3.2.4?

Any reason why you don't use FpDebug instead of GDB ? ... FpDebug is quite good now and odds are reasonably good it does what you need.

[Thaddy]

As I'm currently facing GDB-problems using FPC 3.2.2 (GDB v7.2) I wonder which GDB-version will get linked to the upcoming FPC 3.2.4? I noticed GDB v16.2 is the

You can use GDB as GDB/MI, which is the recommended way. Hard linking libgdb is not recommended for quite some time and afaik it is no longer supported. 3.2.2 uses GDB/MI, so if the problems arise from older code, or older debug practises, change that.
The remark made about fpdebug is correct: it's good.

So: use GDB/MI, or recommended:fpdebug, do not link libgdb anymore.

[Wings2018]

Hello 440bx and Thaddy,

There's no specific reason to not use fpdebug, I simply didn't start with it yet, and I'm also no experienced gdb-user.
I'll find out about fpdebug and see if it supports me in solving my problem, thanks to both of you.

[Martin_fr]

Debugger depends on environment.

FPC (the compiler) does not have any bindings to any gdb or other debugger.

FP (the FPC IDE) use gdb. It used to be libgdb, but now on most targets supposedly is just a gdb instance.
If a gdb instance, then it may be possible (but I do not know) to substitute the gdb exe with a different version.
That said, newer isn't always better, but a matter of trial and error.


All the rest about debugger, is not FPC related. FPC (the compiler) just provides debug info. => OFF TOPIC
The Lazarus IDE comes with FpDebug (for Linux and Windows, and only INTEL/AMD CPU).
For the rest it is gdb. On Linux it uses what is installed by the repo. On Window it still ships an old one, but if you have a newer, well test it.
On Mac, it uses a combination of LLDB+FpDebug (even with the M CPUs).