This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: dynamic array's upper bound evaluated as address for AVR target
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>
- Cc: Pierre-Marie de Rodat <derodat at adacore dot com>, Sivanupandi Pitchumani <Pitchumani dot Sivanupandi at atmel dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>, Andrew Burgess <andrew dot burgess at embecosm dot com>, "tom at tromey dot com" <tom at tromey dot com>
- Date: Wed, 14 Oct 2015 05:26:38 -0700
- Subject: Re: dynamic array's upper bound evaluated as address for AVR target
- Authentication-results: sourceware.org; auth=none
- References: <561E11A2 dot 5030206 at adacore dot com> <20151014094141 dot 54C93DAD at oc7340732750 dot ibm dot com>
> I think the current GDB "dynamic property" mechanism was probably intended
> to capture what DWARF section 2.19 specifies, but due to its simultaneous
> use for DW_AT_data_location and DW_AT_static_link, things got confused.
>
> It would probably be best to clearly separate this out into two separate
> mechanisms, one that precisely implements dynamic properties as defined
> in section 2.19, and one that implements location descriptions. (Note
> that those mechanism should ideally then be used for some of the *other*
> places where the DWARF standard also allows either a dynamic property or
> a location description, but GDB doesn't accept them yet.)
>
> This would then have the side effect that we could distinguish return
> types: location descriptions always return an address, but section 2.19
> dynamic attributes always return an integer.
Sounds correct to me.
--
Joel