On 25/04/2026 00:10, Sven Barth via fpc-devel wrote:
Martin Frb via fpc-devel <[email protected]> schrieb am
Fr., 24. Apr. 2026, 17:13:
See the example below. Complied on Linux and windows. (fpc 3.3.1)
fpc -O- -gw3 project.lpr
then using
strings project | grep TLIST
On linux entries for *all* methods of TList are present.
On Windows that is NOT the case.
On Windows the internal linker can better omit unused sections while
debug information is enabled while with ELF it can't.
Is there an option to turn that "better" off?
As a user (if I hadn't learned how to deal with FPC debug differences to
other development tools), I would expect those not to be stripped.
As a user, if I used a TList in my app, I would want to be able to evaluate
SomeList.GetCount()
This didn't matter when GDB couldn't watch function call results. But
now we have an alternative.
---------------
Actually, what debuggers are used by core team members? Anyone still
using gdb in some cases (including OOP targets?)
---------------
Btw, any idea where the compiler stores the target pointer size?
The code currently uses
tai_const.create_8bit(sizeof(pint))
But that can't be right when cross compiling?
_______________________________________________
fpc-devel maillist - [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
