diff options
author | Tom de Vries <tdevries@suse.de> | 2020-05-06 14:48:50 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2020-05-06 14:48:50 +0200 |
commit | 24fe640b4d2cdb3914254afe2cd02aa31242e4db (patch) | |
tree | 25d9466e23bde6048e452d2ccab87abed9f72a77 /gdb/source.c | |
parent | 0d8683a32122f0027d2ab64082d1f9fced98d599 (diff) | |
download | binutils-24fe640b4d2cdb3914254afe2cd02aa31242e4db.zip binutils-24fe640b4d2cdb3914254afe2cd02aa31242e4db.tar.gz binutils-24fe640b4d2cdb3914254afe2cd02aa31242e4db.tar.bz2 |
[gdb/testsuite] Fix gdb.reverse/consecutive-{precsave,reverse}.exp with gcc-8
When running test-cases gdb.reverse/consecutive-precsave.exp and
gdb.reverse/consecutive-reverse.exp with gcc-8, we get:
...
FAIL: gdb.reverse/consecutive-precsave.exp: stopped at bp, 2nd instr
FAIL: gdb.reverse/consecutive-reverse.exp: stopped at bp, 2nd instr
...
These FAILs are duplicates of the FAILs fixed in commit 7c99e7e2b08
"[gdb/testsuite] Fix gdb.base/consecutive.exp with gcc-8".
Fix these in the same manner.
Tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2020-05-06 Tom de Vries <tdevries@suse.de>
* gdb.reverse/consecutive-precsave.exp: Handle if instruction after
breakpoint is at a "recommended breakpoint location".
* gdb.reverse/consecutive-reverse.exp: Same.
Diffstat (limited to 'gdb/source.c')
0 files changed, 0 insertions, 0 deletions