Martin Frb via fpc-devel schrieb am So.,
26. März 2023, 16:50:
> It also would fall short, if ever Fpc did what Delphi did:
> {$ZEROBASEDSTRINGS }
> Though, maybe that is a "wont ever happen".
>
FPC supports that directive since at least 3.2.0 (though apparently it was
forgotten to be documented
On 26/03/2023 16:50, Martin Frb via fpc-devel wrote:
On 26/03/2023 15:50, Florian Klämpfl via fpc-devel wrote:
What about using DW_TAG_string_type for this? IIRC, when I
implemented dwarf, it was not available/not supported, but fpdebug
can do they. I am not sure about the status of GDB about i
On 26/03/2023 15:50, Florian Klämpfl via fpc-devel wrote:
Am 23.03.23 um 09:45 schrieb Martin Frb via fpc-devel:
It's a little hard to comment all at once, but at least I start with
one :)
4) "official" marker for string vs pchar vs array
What about using DW_TAG_string_type for this? IIRC
Am 23.03.23 um 09:45 schrieb Martin Frb via fpc-devel:
It's a little hard to comment all at once, but at least I start with one :)
4) "official" marker for string vs pchar vs array
Not sure if that is reported already. Depending on dwarf version
"string" (ansistring) is a pointer (either TAG
After the brief exchange on
https://gitlab.com/freepascal.org/fpc/source/-/issues/40208
There are various considerations (ideas/requests) to hopefully help
improve debugging experience.
I have recently added 3 issues, but there is more. And I wanted to add a
bit of background here, since it
