[fpc-devel] FPC 64bit and gdb on Linux

Bruce Bauman bruce.bauman at andesaservices.com
Mon Oct 26 14:57:07 CET 2009


Does this mean the 32-bit version of FPC generates STABS and the 64-bit
version generates DWARF?

If my goal was to use gdb on a large application written in Pascal, am I
better off using the 32-bit version because the debugger support is
better?

Also, I'm assuming it's the DWARF parser in gdb that needs "fixing". Is
this specific to Pascal, or is the DWARF support generally broken?

I'm pretty confused by this...

-- Bruce

-----Original Message-----
From: fpc-devel-bounces at lists.freepascal.org
[mailto:fpc-devel-bounces at lists.freepascal.org] On Behalf Of Jonas Maebe
Sent: Friday, October 23, 2009 4:10 PM
To: FPC developers' list; Martin Schreiber
Subject: Re: [fpc-devel] FPC 64bit and gdb on Linux

Martin Schreiber wrote on Fri, 23 Oct 2009:

> Why is it not possible to set a breakpoint to "test"?

You have to use TEST. This is the same for Stabs on 32 bit platforms,  
afaik: you always have to use the uppercase name for setting  
breakpoints on procedures/functions.

> Is it as designed that the displayed value of a var parameter is the
address
> instead the value?

It's because nobody bothered to submit a patch to GDB yet to add  
support for var parameters in their DWARF parser, so we currently  
encode them as C++-style references. That's the way references are  
displayed by GDB.


Jonas

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
fpc-devel maillist  -  fpc-devel at lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
CONFIDENTIALITY NOTICE: This e-mail is confidential and intended
solely for the use of the individual or entity to which it is addressed.  If
you are not the intended recipient, be advised that you have received 
this email in error and that any use, dissemination, forwarding, printing 
or copying of this e-mail is strictly prohibited. If you received this e-mail
in error, please delete it from your computer and contact the sender.




More information about the fpc-devel mailing list