aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base/code_elim1.c
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2013-08-30 15:37:37 +0000
committerPedro Alves <palves@redhat.com>2013-08-30 15:37:37 +0000
commit02457c768f78754f76d81b241236338ee2e28a86 (patch)
treeb3e327bfaafa6a149c5ad1999a315ec30f04fe67 /gdb/testsuite/gdb.base/code_elim1.c
parente0162910f16c309b8bc642cfb1558babe92993f7 (diff)
downloadgdb-02457c768f78754f76d81b241236338ee2e28a86.zip
gdb-02457c768f78754f76d81b241236338ee2e28a86.tar.gz
gdb-02457c768f78754f76d81b241236338ee2e28a86.tar.bz2
MI -trace-find, print frame with LOC_AND_ADDRESS instead of SRC_AND_LOC.
When I looked for print_stack_frame calls in MI, I wondered why this one passing down SRC_AND_LOC. print_stack_frame does: /* For mi, alway print location and address. */ if (ui_out_is_mi_like_p (current_uiout)) print_what = LOC_AND_ADDRESS; So it really doesn't matter which value is passed down, but, to avoid confusion in readers, it's better to use the MI standard here. There's another SRC_AND_LOC in mi-interp.c, but that one makes sense. gdb/ 2013-08-30 Pedro Alves <palves@redhat.com> * mi/mi-main.c (mi_cmd_trace_find): Use LOC_AND_ADDRESS instead of SRC_AND_LOC.
Diffstat (limited to 'gdb/testsuite/gdb.base/code_elim1.c')
0 files changed, 0 insertions, 0 deletions