diff options
| author | Sanimir Agovic <sanimir.agovic@intel.com> | 2013-10-09 15:28:22 +0100 |
|---|---|---|
| committer | Sanimir Agovic <sanimir.agovic@intel.com> | 2014-04-11 13:43:48 +0100 |
| commit | 37c1ab67a35025d37d42c449deab5f254f9f59da (patch) | |
| tree | 58b22b4d781f80685e330c47d41571991a082fa2 /gdb/valops.c | |
| parent | 729efb13174d6522fba4aa7ab273e7f25a253c47 (diff) | |
| download | gdb-37c1ab67a35025d37d42c449deab5f254f9f59da.zip gdb-37c1ab67a35025d37d42c449deab5f254f9f59da.tar.gz gdb-37c1ab67a35025d37d42c449deab5f254f9f59da.tar.bz2 | |
type: add c99 variable length array support
The dwarf standard allow certain attributes to be expressed as dwarf
expressions rather than constants. For instance upper-/lowerbound attributes.
In case of a c99 variable length array the upperbound is a dynamic attribute.
With this change c99 vla behave the same as with static arrays.
1| void foo (size_t n) {
2| int ary[n];
3| memset(ary, 0, sizeof(ary));
4| }
(gdb) print ary
$1 = {0 <repeats 42 times>}
* dwarf2loc.c (dwarf2_locexpr_baton_eval): New function.
(dwarf2_evaluate_property): New function.
* dwarf2loc.h (dwarf2_evaluate_property): New function prototype.
* dwarf2read.c (attr_to_dynamic_prop): New function.
(read_subrange_type): Use attr_to_dynamic_prop to read high bound
attribute.
* gdbtypes.c: Include dwarf2loc.h.
(is_dynamic_type): New function.
(resolve_dynamic_type): New function.
(resolve_dynamic_bounds): New function.
(get_type_length): New function.
(check_typedef): Use get_type_length to compute type length.
* gdbtypes.h (TYPE_HIGH_BOUND_KIND): New macro.
(TYPE_LOW_BOUND_KIND): New macro.
(is_dynamic_type): New function prototype.
* value.c (value_from_contents_and_address): Call resolve_dynamic_type
to resolve dynamic properties of the type. Update comment.
* valops.c (get_value_at, value_at, value_at_lazy): Update comment.
Diffstat (limited to 'gdb/valops.c')
| -rw-r--r-- | gdb/valops.c | 15 |
1 files changed, 12 insertions, 3 deletions
diff --git a/gdb/valops.c b/gdb/valops.c index 1fa188f..46e2639 100644 --- a/gdb/valops.c +++ b/gdb/valops.c @@ -900,7 +900,10 @@ value_one (struct type *type) return val; } -/* Helper function for value_at, value_at_lazy, and value_at_lazy_stack. */ +/* Helper function for value_at, value_at_lazy, and value_at_lazy_stack. + The type of the created value may differ from the passed type TYPE. + Make sure to retrieve the returned values's new type after this call + e.g. in case the type is a variable length array. */ static struct value * get_value_at (struct type *type, CORE_ADDR addr, int lazy) @@ -925,7 +928,10 @@ get_value_at (struct type *type, CORE_ADDR addr, int lazy) value_at_lazy instead. value_at_lazy simply records the address of the data and sets the lazy-evaluation-required flag. The lazy flag is tested in the value_contents macro, which is used if and when - the contents are actually required. + the contents are actually required. The type of the created value + may differ from the passed type TYPE. Make sure to retrieve the + returned values's new type after this call e.g. in case the type + is a variable length array. Note: value_at does *NOT* handle embedded offsets; perform such adjustments before or after calling it. */ @@ -936,7 +942,10 @@ value_at (struct type *type, CORE_ADDR addr) return get_value_at (type, addr, 0); } -/* Return a lazy value with type TYPE located at ADDR (cf. value_at). */ +/* Return a lazy value with type TYPE located at ADDR (cf. value_at). + The type of the created value may differ from the passed type TYPE. + Make sure to retrieve the returned values's new type after this call + e.g. in case the type is a variable length array. */ struct value * value_at_lazy (struct type *type, CORE_ADDR addr) |