Remove setup_kfail server/13796 in disp-step-syscall.exp

This patch series add fork support in target remote,

  [PATCH v2 0/3] Target remote mode fork and exec support
  https://sourceware.org/ml/gdb-patches/2015-12/msg00144.html

so GDB can be informed about the child, and adjust child correctly in
displaced stepping.  The PR server/13796 was fixed by this patch
series actually.  Test results on buildbot show this KFAIL->KPASS
change https://sourceware.org/ml/gdb-testers/2015-q4/msg10128.html

gdb/testsuite:

2016-02-18  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/disp-step-syscall.exp (disp_step_cross_syscall):
	Don't call setup_kfail.
This commit is contained in:
Yao Qi 2016-02-18 13:02:12 +00:00
parent 40fb20d037
commit 2d5189bd3a
2 changed files with 5 additions and 6 deletions

View File

@ -1,3 +1,8 @@
2016-02-18 Yao Qi <yao.qi@linaro.org>
* gdb.base/disp-step-syscall.exp (disp_step_cross_syscall):
Don't call setup_kfail.
2016-02-18 Yao Qi <yao.qi@linaro.org>
* gdb.threads/forking-threads-plus-breakpoint.exp (do_test):

View File

@ -49,8 +49,6 @@ proc disp_step_cross_syscall { syscall } {
return
}
set is_target_remote [gdb_is_target_remote]
# Delete the breakpoint on main.
gdb_test_no_output "delete break 1"
@ -130,10 +128,6 @@ proc disp_step_cross_syscall { syscall } {
gdb_test_no_output "set displaced-stepping on"
# Check the address of next instruction of syscall.
if {$syscall == "vfork" && $is_target_remote} {
setup_kfail server/13796 "*-*-*"
}
if {[gdb_test "stepi" "x/i .*=>.*" "single step over $syscall"] != 0} {
return -1
}