diff options
| author | Andreas Arnez <arnez@linux.vnet.ibm.com> | 2016-10-05 12:36:29 +0200 |
|---|---|---|
| committer | Andreas Arnez <arnez@linux.vnet.ibm.com> | 2016-10-05 12:36:29 +0200 |
| commit | f206f69cb43e420f92a63464036b342386963261 (patch) | |
| tree | 4f7cf4be286e39dca00d95226b3aacfe35f42fc8 /gdb/ChangeLog | |
| parent | ed2f09e183df513e9616c53cdace32cf8b824b98 (diff) | |
| download | gdb-f206f69cb43e420f92a63464036b342386963261.zip gdb-f206f69cb43e420f92a63464036b342386963261.tar.gz gdb-f206f69cb43e420f92a63464036b342386963261.tar.bz2 | |
Allow DW_OP_GNU_uninit in dwarf_expr_require_composition
In DWARF expression handling, some operators are required to be either
at the end of an expression or followed by a composition operator. So
far only the operators DW_OP_reg0-31 were allowed to be followed by
DW_OP_GNU_uninit instead, and particularly DW_OP_regx was not, which is
obviously inconsistent.
This patch allows DW_OP_GNU_uninit after all operators requiring a
composition, to simplify the code and make it more consistent. This
policy may be more permissive than necessary, but in the worst case just
leads to a DWARF location description resulting in an uninitialized
value instead of an error message.
gdb/ChangeLog:
* dwarf2expr.c (dwarf_expr_require_composition): Allow
DW_OP_GNU_uninit.
(execute_stack_op): Use dwarf_expr_require_composition instead of
copying its logic.
Diffstat (limited to 'gdb/ChangeLog')
| -rw-r--r-- | gdb/ChangeLog | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 357f648..eaef0b0 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,10 @@ +2016-10-05 Andreas Arnez <arnez@linux.vnet.ibm.com> + + * dwarf2expr.c (dwarf_expr_require_composition): Allow + DW_OP_GNU_uninit. + (execute_stack_op): Use dwarf_expr_require_composition instead of + copying its logic. + 2016-10-05 Anton Kolesov <anton.kolesov@synopsys.com> arc-tdep.c (arc_frame_prev_register): Remove annoying log message. |