[fpc-devel] win64 dwarf patch
Pierre Free Pascal
pierre at freepascal.org
Thu Oct 14 00:17:16 CEST 2010
> -----Message d'origine-----
> De : fpc-devel-bounces at lists.freepascal.org [mailto:fpc-devel-
> bounces at lists.freepascal.org] De la part de Willibald Krenn
> Envoyé : Wednesday, October 13, 2010 11:53 PM
> À : fpc-devel at lists.freepascal.org
> Objet : Re: [fpc-devel] win64 dwarf patch
>
> Am 13.10.2010 21:34, schrieb Willibald Krenn:
> > Yes, your output seems to be fine! I'll try upgrading my gdb to a
> newer
> > version - hope this helps. If this is working, then I think we should
> > switch to DWARF2 on Win64 and close all related bugs in mantis. ;-)
>
> I upgraded my version of gdb and that fixed the problem. Small
> disadvantage, though: DWARF debug info disables smart linking :-(.
>
> Anyway, while fpc and gdb are working now, Lazarus fails to pick up the
> correct address if it is outside of the 32 bit range:
>
> <info address FPC_RAISEEXCEPTION>
> &"info address FPC_RAISEEXCEPTION\n"
> ~"Symbol \"FPC_RAISEEXCEPTION\" is at 0x100008a30 in a file compiled
> without debugging.\n"
> ^done
> (gdb)
> <-break-insert *35376>
> ^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="
> 0x0000000000008a30",at="",times="0",original-location="*35376"}
> (gdb)
This seems like a Lazarus specific problem,
the address is certainly cropped to 32-bit somewhere...
I am sorry, but I know almost nothing about
Lazarus source code, so you will need to find someone else
to fix this.
An interesting piece of information
would be to know if x86_64-linux is working
without this limitation.
Pierre
More information about the fpc-devel
mailing list