On 26 Oct 2009, at 14:57, Bruce Bauman wrote:
Does this mean the 32-bit version of FPC generates STABS and the 64-
bit
version generates DWARF?
By default, yes. You can also force the 32 bit version generate DWARF
by using -gw2 rather than -g
If my goal was to use gdb on a large applicat
ebe
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
On Saturday 24 October 2009 18:32:32 JoshyFun wrote:
> Hello Martin,
>
> Saturday, October 24, 2009, 10:42:27 AM, you wrote:
>
> MS> What do you recommend, should MSEide parse the gdb watch results and
> run MS> another query in order to get the values of var parameters? How
> does Lazarus MS> solv
Martin Schreiber wrote on Sat, 24 Oct 2009:
I do not know the different debug formats, is it correct that FPC uses STABS
on x86 and DWARF on x64?
Yes. The reason is that Stabs is defined as a 32 bit format and does
not work for 64 bit.
What do you recommend, should MSEide parse the gdb wa
On Friday 23 October 2009 22:09:30 you wrote:
> Martin Schreiber wrote on Fri, 23 Oct 2009:
>
> > 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
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 tha
