aboutsummaryrefslogtreecommitdiff
path: root/opcodes/i386-gen.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2020-10-14 13:17:58 +0200
committerTom de Vries <tdevries@suse.de>2020-10-14 13:17:58 +0200
commit8c8bd0babc6039a4cef7d60d57b1b68e7a7f2e70 (patch)
treef197f37a8b4fe365e6034530e16fc58c46c97847 /opcodes/i386-gen.c
parent76547ab31b16b521e29892cab5a29b60b52291a5 (diff)
downloadgdb-8c8bd0babc6039a4cef7d60d57b1b68e7a7f2e70.zip
gdb-8c8bd0babc6039a4cef7d60d57b1b68e7a7f2e70.tar.gz
gdb-8c8bd0babc6039a4cef7d60d57b1b68e7a7f2e70.tar.bz2
[gdb/testsuite] Fix gdb.ada/mi_catch_ex{,_hand}.exp FAILs
The test-case gdb.ada/mi_catch_ex.exp tests two scenarios. The two scenarios are separated by: - a mi_run_to_main (before commit b75d55d4d2 "Eliminate mi_run_to_main, introduce mi_clean_restart") - a mi_runto_main (after that commit) The now removed mi_run_to_main contained a mi_delete_breakpoints, while mi_runto_main does not, which causes FAILs in the second scenario. Fix this by adding the missing mi_delete_breakpoints in the test-case, and likewise in gdb.ada/mi_catch_ex_hand.exp. Reg-tested on x86_64-linux. gdb/testsuite/ChangeLog: 2020-10-14 Tom de Vries <tdevries@suse.de> PR testsuite/26732 * gdb.ada/mi_catch_ex.exp: Do mi_delete_breakpoints before running scenario 2. * gdb.ada/mi_catch_ex_hand.exp: Same.
Diffstat (limited to 'opcodes/i386-gen.c')
0 files changed, 0 insertions, 0 deletions