OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[gdb/testsuite] Fix duplicate test-names in gdb.ada 

In gdb.ada we have these duplicate test-names:
...
DUPLICATE: gdb.ada/catch_ex.exp: continuing to program completion
DUPLICATE: gdb.ada/mi_catch_ex.exp: breakpoint at main
DUPLICATE: gdb.ada/mi_catch_ex.exp: mi runto main
DUPLICATE: gdb.ada/mi_catch_ex_hand.exp: breakpoint at main
DUPLICATE: gdb.ada/mi_catch_ex_hand.exp: mi runto main
...

Fix these using with_test_prefix.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2020-05-12  Tom de Vries  <tdevries@suse.de>

	* gdb.ada/catch_ex.exp: Use with_test_prefix.
	* gdb.ada/mi_catch_ex.exp: Same.
	* gdb.ada/mi_catch_ex_hand.exp: Same.
This commit is contained in:
Tom de Vries 2020-05-12 11:05:44 +02:00
parent 7549fed824
commit dbb0ab10dd
4 changed files with 31 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,9 @@
2020-05-12 Tom de Vries <tdevries@suse.de>
* gdb.ada/catch_ex.exp: Use with_test_prefix.
* gdb.ada/mi_catch_ex.exp: Same.
* gdb.ada/mi_catch_ex_hand.exp: Same.
2020-05-12 Tom de Vries <tdevries@suse.de>
* gdb.fortran/complex.exp: Use with_test_prefix.

9
gdb/testsuite/gdb.ada/catch_ex.exp
View File

@ -162,9 +162,10 @@ gdb_test "continue" \
"Continuing\.$eol$temp_catchpoint_msg$eol.*SPOT1" \
"continuing to temporary catchpoint"
gdb_test "continue" \
"Continuing\..*$inferior_exited_re.*" \
"continuing to program completion"
with_test_prefix "temporary catchpoint" {
gdb_test "continue" \
"Continuing\..*$inferior_exited_re.*" \
"continuing to program completion"
}

16
gdb/testsuite/gdb.ada/mi_catch_ex.exp
View File

@ -69,9 +69,11 @@ mi_gdb_load ${binfile}
# 1. Try catching all exceptions. #
####################################
if ![mi_run_to_main] then {
fail "cannot run to main, testcase aborted"
return 0
with_test_prefix "scenario 1" {
if ![mi_run_to_main] then {
fail "cannot run to main, testcase aborted"
return 0
}
}
mi_gdb_test "-catch-exception" \
@ -125,9 +127,11 @@ continue_to_exception \
# - continue, we should see the unhandled Constrait_Error exception
# - continue, the program exits.
if ![mi_run_to_main] then {
fail "cannot run to main, testcase aborted"
return 0
with_test_prefix "scenario 2" {
if ![mi_run_to_main] then {
fail "cannot run to main, testcase aborted"
return 0
}
}
mi_gdb_test "-catch-exception -e Program_Error" \

16
gdb/testsuite/gdb.ada/mi_catch_ex_hand.exp
View File

@ -64,9 +64,11 @@ if [mi_gdb_start] {
# 1. Try catching all exceptions handlers. #
#############################################
if ![mi_run_to_main] then {
fail "cannot run to main, testcase aborted"
return 0
with_test_prefix "scenario 1" {
if ![mi_run_to_main] then {
fail "cannot run to main, testcase aborted"
return 0
}
}
mi_gdb_test "-catch-handlers" \
@ -114,9 +116,11 @@ continue_to_exception_handler \
# - continue, we should not stop at the Program_Error exception handler
# but exit instead.
if ![mi_run_to_main] then {
fail "cannot run to main, testcase aborted"
return 0
with_test_prefix "scenario 2" {
if ![mi_run_to_main] then {
fail "cannot run to main, testcase aborted"
return 0
}
}
mi_gdb_test "-catch-handlers -e Constraint_Error" \