Ok, thanks for the hint!
Pascal
> Joost van der Sluis via lazarus hat am
> 29.06.2022 12:11 CEST geschrieben:
>
>
> Op 29-06-2022 om 10:31 schreef Pascal Riekenberg via lazarus:
> > I use fpc trunk (3.3.1)
>
> Seems there is a problem in the internal linker on Windows. It does not
> prope
Op 29-06-2022 om 10:31 schreef Pascal Riekenberg via lazarus:
I use fpc trunk (3.3.1)
Seems there is a problem in the internal linker on Windows. It does not
properly relocate the CFI information.
You can compile with '-Xe' to use the external linker. That also fixes
this problem and this w
I use fpc trunk (3.3.1)
Pascal
> Joost van der Sluis via lazarus hat am
> 29.06.2022 10:23 CEST geschrieben:
>
>
> Op 29-06-2022 om 09:59 schreef Pascal Riekenberg via lazarus:
> > i did this to temporary solve it for me:
> >
> > components/fpdebug/fpdbgdwarfdataclasses.pas | 3 ++-
> >
Op 29-06-2022 om 09:59 schreef Pascal Riekenberg via lazarus:
i did this to temporary solve it for me:
components/fpdebug/fpdbgdwarfdataclasses.pas | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
I've committed something similar. I suppose you are using fpc 3.2.3?
Regards,
Joost
Hi Joost,
i did this to temporary solve it for me:
components/fpdebug/fpdbgdwarfdataclasses.pas | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/components/fpdebug/fpdbgdwarfdataclasses.pas
b/components/fpdebug/fpdbgdwarfdataclasses.pas
index 67c715b762..e62726658b 100644
-
Hi Joost,
i think i have a problem with this. When starting to debug with FpDebug on
Windows 10 64bit i get the following error:
TApplication.HandleException: EListError
Duplicate ID:
Stack trace:
$0001001EA1CF Error, line 383 of maps.pp
$0001001E9DF8 InternalAdd
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@lists.lazarus-ide.org> wrote:
>
> Hi all,
>
> I've ju
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
