diff options
author | Tom de Vries <tdevries@suse.de> | 2022-08-05 08:09:57 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2022-08-05 08:09:57 +0200 |
commit | 731d2cc1d5106c077584bd83e96dbba4f7e11118 (patch) | |
tree | f76ffb66c77d08c5ac0840ac459435fa7b69a4d9 /gas | |
parent | 701821154b110230f52a0367e120ecc51f490e56 (diff) |
[gdb] Add debug_{exp,val}linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allmodconfiglinaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfiglinaro-local/ci/tcwg_kernel/gnu-master-arm-lts-allyesconfiglinaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allnoconfiglinaro-local/ci/tcwg_bmk_llvm_fx/llvm-master-aarch64-spec2k6-O2
When debugging cc1 I heavily rely on simple one-parameter debug functions
that allow me to inspect a variable of a common type, like:
- debug_generic_expr
- debug_gimple_stmt
- debug_rtx
and I miss similar functions in gdb.
Add functions to dump variables of types 'value' and 'expression':
- debug_exp, and
- debug_val.
Tested on x86_64-linux, by breaking on varobj_create, and doing:
...
(gdb) call debug_exp (var->root->exp.get ())
&"Operation: OP_VAR_VALUE\n"
&" Block symbol:\n"
&" Symbol: aaa\n"
&" Block: 0x2d064f0\n"
(gdb)
...
and:
...
(gdb) call debug_val (value)
&"5"
(gdb)
...
Diffstat (limited to 'gas')
0 files changed, 0 insertions, 0 deletions