[10/11] gdb, testsuite: add kfails for step-over-process-exit.exp
Checks
| Context |
Check |
Description |
| linaro-tcwg-bot/tcwg_gdb_build--master-aarch64 |
success
|
Build passed
|
| linaro-tcwg-bot/tcwg_gdb_build--master-arm |
success
|
Build passed
|
| linaro-tcwg-bot/tcwg_gdb_check--master-aarch64 |
success
|
Test passed
|
| linaro-tcwg-bot/tcwg_gdb_check--master-arm |
success
|
Test passed
|
Commit Message
From: "Bouhaouel, Mohamed" <mohamed.bouhaouel@intel.com>
When running 'gdb.threads/step-over-process-exit.exp' against a
remote target in non-stop mode, GDB fails with a "Remote
communication error" and does not display the expected
"[Inferior ... exited normally]" message. The test passes in
all-stop mode but fails when target-non-stop is enabled.
Mark the affected assertions as kfail referencing the bug report
gdb/34142 until the underlying issue is resolved.
---
gdb/testsuite/gdb.threads/step-over-process-exit.exp | 6 ++++++
1 file changed, 6 insertions(+)
@@ -35,6 +35,11 @@ if { [prepare_for_testing "failed to prepare" $testfile $srcfile {debug pthread}
# thread, or "other" for the non-main thread.
proc test {which} {
+ if {$which == "other"} {
+ # The failure from the first iteration prevents
+ # the second iteration to run.
+ setup_kfail "gdb/34142" "*-*-*"
+ }
if {![runto_main]} {
return -1
}
@@ -48,6 +53,7 @@ proc test {which} {
set target_non_stop [is_target_non_stop]
+ setup_kfail "gdb/34142" "*-*-*"
gdb_test_multiple "next" "" {
-re -wrap "$::inferior_exited_re normally\\\]" {
pass $gdb_test_name