Mark> To make it possible to quickly see whether an address (range) is covered
Mark> by an ELF file containing DWARF information two proposals were made:
I finally read through this thread.
Cary> I think it's fine for a consumer to first assume that the
Cary> .debug_aranges table is complete, but
Jakub> That's strange, for Fortran arrays GCC emits DW_OP_push_object_address
Jakub> heavily.
AFAICT it's never come "seriously" to anybody's attention.
Looking at bugzilla I do see:
https://sourceware.org/bugzilla/show_bug.cgi?id=8041
Can you send me a test case off list? It can't use Fortran
> > Just to address the gdb part -- the only reason this isn't implemented
> > is that presumably no gdb developer has ever encountered a compiler that
> > emits it. It shouldn't be hard to add should you need it. Please file
> > a bug in gdb bugzilla.
>
> That's strange, for Fortran arrays GCC
On Wed, Apr 23, 2014 at 08:14:56AM -0600, Tom Tromey wrote:
> Pierre-Marie> I tried to look at the implementation of
> Pierre-Marie> DW_OP_push_object_address in GDB, but it looks like it's
> Pierre-Marie> not implemented yet. What do you think about its expected
> Pierre-Marie> behavior? And if I
Pierre-Marie> I tried to look at the implementation of
Pierre-Marie> DW_OP_push_object_address in GDB, but it looks like it's
Pierre-Marie> not implemented yet. What do you think about its expected
Pierre-Marie> behavior? And if I cannot use this operation for such
Pierre-Marie> array bound express
On 04/23/14 04:46, Mark Wielaard wrote:
On Tue, 2014-04-22 at 10:07 -0700, Michael Eager wrote:
On 04/22/14 03:57, Mark Wielaard wrote:
Assuming the consumer is interested in "the object is not available for
the portion of the range that is not covered" property of the location
list then it lo
Hi,
I'm working on improvements for the DWARF information produced by GCC
for Ada, and I have hit the following issue:
In Ada, it is possible to define array types inside structures (that are
called records). The size of such array types can then depend on members
of such records. For instan
Hi -
On Wed, Apr 23, 2014 at 01:46:30PM +0200, Mark Wielaard wrote:
> [...]
> > > So if a producer wants to take advantage of a default location list
> > > entry to encode a smaller location list for an object, then how should
> > > it present to the consumer the same "not available" information?
On Tue, 2014-04-22 at 10:07 -0700, Michael Eager wrote:
> On 04/22/14 03:57, Mark Wielaard wrote:
>
> > Assuming the consumer is interested in "the object is not available for
> > the portion of the range that is not covered" property of the location
> > list then it looks like if the producer us
