diff options
| author | Zoran Zaric <Zoran.Zaric@amd.com> | 2020-10-14 10:44:56 +0100 |
|---|---|---|
| committer | Zoran Zaric <zoran.zaric@amd.com> | 2021-11-05 11:46:38 +0000 |
| commit | c99af81b30a6f5ab94fafd0dcdea8aa9d92f3ac4 (patch) | |
| tree | 172d42f1a9576c36dff841c2b8583ce35a0c32a2 | |
| parent | a572357c566093a2a4541e60ce177d04b55afb8a (diff) | |
| download | binutils-gdb-c99af81b30a6f5ab94fafd0dcdea8aa9d92f3ac4.tar.gz | |
Add frame info check to DW_OP_reg operations
After enabling location description to be on a DWARF stack, it is now
needed to check the frame context information validity when creating a
register location description.
gdb/ChangeLog:
* dwarf2/expr.c (dwarf_expr_context::execute_stack_op): Add
check_frame_info call for DW_OP_reg operations.
| -rw-r--r-- | gdb/dwarf2/expr.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/gdb/dwarf2/expr.c b/gdb/dwarf2/expr.c index 15164babdd6..2555f9969ef 100644 --- a/gdb/dwarf2/expr.c +++ b/gdb/dwarf2/expr.c @@ -3296,6 +3296,7 @@ dwarf_expr_context::execute_stack_op (const gdb_byte *op_ptr, case DW_OP_reg31: case DW_OP_regx: { + ensure_have_frame (this->m_frame, "DW_OP_reg"); ULONGEST result; if (op == DW_OP_regx) |