aboutsummaryrefslogtreecommitdiff
path: root/gdb/m32r-linux-nat.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2021-09-09 12:29:40 +0200
committerTom de Vries <tdevries@suse.de>2021-09-09 12:29:40 +0200
commit5b99c5718f1c0a4937b4bcce1735311c39578002 (patch)
tree6ecbea8b73b1682830086299677888f21c44409b /gdb/m32r-linux-nat.c
parent86fe51fcc7a78def0b3ed289c0e1e7e8af283acc (diff)
downloadgdb-5b99c5718f1c0a4937b4bcce1735311c39578002.zip
gdb-5b99c5718f1c0a4937b4bcce1735311c39578002.tar.gz
gdb-5b99c5718f1c0a4937b4bcce1735311c39578002.tar.bz2
[gdb/testsuite] Fix various issues in gdb.mi/mi-sym-info.exp
I noticed this failure in gdb.mi/mi-sym-info.exp with gcc-4.8: ... FAIL: gdb.mi/mi-sym-info.exp: -symbol-info-functions --max-results 1 \ (unexpected output) ... due to function f2 instead of f3 being listed. AFAICT, this is caused by a difference in debug info: ... $ readelf -wi outputs/gdb.mi/mi-sym-info/mi-sym-info1.o \ | egrep "DW_AT_name.*: f[1-3]" <72> DW_AT_name : f1 <a1> DW_AT_name : f2 <d0> DW_AT_name : f3 ... vs: ... $ readelf -wi outputs/gdb.mi/mi-sym-info/mi-sym-info1.o \ | egrep "DW_AT_name.*: f[1-3]" <f4> DW_AT_name : f3 <123> DW_AT_name : f2 <152> DW_AT_name : f1 ... and the command documentation does not mention an imposed order, so fix this by allowing f2 as well. Doing this fix, it made sense to do a refactoring of adding f2_re and f3_re variables, in order to write (?:$f2_re|$f3_re), and I applied the same pattern overall. Furthermore, I found a silent FAIL due to calling mi_gdb_proc with 2 args, fix by updating the regexp. Then I ran with clang and found another FAIL, fix by updating the regexp. Tested on x86_64-linux with gcc-4.8.5, gcc-7.5.0, gcc-11.2.1, clang-7.0.1 and clang-12.0.1.
Diffstat (limited to 'gdb/m32r-linux-nat.c')
0 files changed, 0 insertions, 0 deletions