[Lazarus] CFI in FpDebug

[Christo Crause]

Great news, thank you Joost. This should decrease the amount of code memory
that needs to be scanned when building a stack trace - a boost particularly
for remote debugging.

On Tue, 28 Jun 2022, 23:22 Joost van der Sluis via lazarus, <
lazarus at lists.lazarus-ide.org> wrote:

>
> Hi all,
>
> I've just pushed a commit that changed the stack-unwinding logic for
> FpDebug.
>
> What is new is that when the executable includes Call Frame Information
> (CFI) as specified by the Dwarf-format and CFI is available for the a
> certain location, the CFI is used to unwind the stack. (x86_64 and i386
> only)
>
> Note however, that the CFI generated by FPC is not always correct, but
> in those cases is should fallback to the old implementation.
>
> In principle things could only get better. But if not, please tell me.
>
> Regards,
>
> Joost.
> --
> _______________________________________________
> lazarus mailing list
> lazarus at lists.lazarus-ide.org
> https://lists.lazarus-ide.org/listinfo/lazarus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20220629/7677d040/attachment.htm>