This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Improve stabs debugging for mingw64 executables loaded at high addresses
- From: Tristan Gingold <gingold at adacore dot com>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: <gdb-patches at sourceware dot org>
- Date: Wed, 15 Sep 2010 09:29:23 +0200
- Subject: Re: [RFC] Improve stabs debugging for mingw64 executables loaded at high addresses
- References: <000701cb541e$1160cde0$342269a0$@muller@ics-cnrs.unistra.fr> <282E4D5B-2863-4CC2-99EE-76A36BDE8A9F@adacore.com> <000a01cb5420$e7a44420$b6eccc60$@muller@ics-cnrs.unistra.fr>
On Sep 14, 2010, at 5:24 PM, Pierre Muller wrote:
>>> Comments welcome,
>>
>> I think that some 64 bits targets have 8 bytes for the address.
>
>
> Of course, dwarf debugging doesn't suffer from this limitation,
> and uses 8-byte for addresses.
> This is the default format for most 64-bit targets,
> and it is the preferred debugging format for 64-bit
> because of this 4-byte limitation of stabs...
> So this is really a marginal case that I presented here.
To clarify, I meant that some 64 bits targets have 8 bytes for the address in *stabs*.
(eg: darwin64 - but the use of stabs is deprecated for this target).
OTOH, dbxread.c seems to be bound to 32-bits stabs address.
I am not sure it is right to set objfile->section_offsets->offsets.
> The thing is that, for Free Pascal, we have lots of
> troubles with DWARF (and some 64-bit specific),
> thus I would like to be able to use STABS format (which
> is less troublesome) but that also didn't work
> because of this high address default base used by this compiler.
So, it might be worth fixing Free Pascal too !
Tristan.