On 04/23/2014 04:14 PM, Tom Tromey wrote:
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.
As a matter of
On 04/23/2014 04:34 PM, Tom Tromey wrote:
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 for more information about DW_OP_push_object_address, I found a
thread from 2007[1] in whi
On 04/24/14 01:38, Mark Wielaard wrote:
Hi Michael,
On Wed, 2014-04-23 at 06:54 -0700, Michael Eager wrote:
On 04/23/14 04:46, Mark Wielaard wrote:
An alternate might be to include a location list entry for the range
where the object is not available and have that contain a zero-length
locatio
Hi Tom,
On Wed, 2014-04-23 at 09:01 -0600, Tom Tromey wrote:
> 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 con
Hi Michael,
On Wed, 2014-04-23 at 06:54 -0700, Michael Eager wrote:
> On 04/23/14 04:46, Mark Wielaard wrote:
> >> An alternate might be to include a location list entry for the range
> >> where the object is not available and have that contain a zero-length
> >> location list. That would be non-
On Wed, 2014-04-23 at 08:49 -0400, Frank Ch. Eigler wrote:
> 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
