diff options
author | Pedro Alves <palves@redhat.com> | 2018-03-25 18:02:43 +0100 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2018-03-25 18:56:58 +0100 |
commit | 3e5ef9a4de7919971130f7f2ca3052898a069e76 (patch) | |
tree | 67a24bdf90eb1f9b05f5fa1777f555b8f71c779e /gdb/eval.c | |
parent | c88d2fccb148d38ca53d379b7b71eb0467e1a2cc (diff) | |
download | gdb-3e5ef9a4de7919971130f7f2ca3052898a069e76.zip gdb-3e5ef9a4de7919971130f7f2ca3052898a069e76.tar.gz gdb-3e5ef9a4de7919971130f7f2ca3052898a069e76.tar.bz2 |
eval.c: reverse minsym and sym
I noticed that in evaluate_funcall, where we handle
OP_VAR_MSYM_VALUE/OP_VAR_VALUE to figure out the symbol's name gets
the minimal_symbol/symbol backwards. Happens to be harmless in
practice because the symbol name is recorded in the common initial
sequence (in the general_symbol_info field).
gdb/ChangeLog:
2018-03-25 Pedro Alves <palves@redhat.com>
* eval.c (evaluate_funcall): Swap OP_VAR_MSYM_VALUE/OP_VAR_VALUE
if then/else bodies in var_func_name extraction.
Diffstat (limited to 'gdb/eval.c')
-rw-r--r-- | gdb/eval.c | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -1039,13 +1039,13 @@ evaluate_funcall (type *expect_type, expression *exp, int *pos, { if (op == OP_VAR_MSYM_VALUE) { - symbol *sym = exp->elts[*pos + 2].symbol; - var_func_name = SYMBOL_PRINT_NAME (sym); + minimal_symbol *msym = exp->elts[*pos + 2].msymbol; + var_func_name = MSYMBOL_PRINT_NAME (msym); } else if (op == OP_VAR_VALUE) { - minimal_symbol *msym = exp->elts[*pos + 2].msymbol; - var_func_name = MSYMBOL_PRINT_NAME (msym); + symbol *sym = exp->elts[*pos + 2].symbol; + var_func_name = SYMBOL_PRINT_NAME (sym); } argvec[0] = evaluate_subexp_with_coercion (exp, pos, noside); |