From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Remove setup_kfail server/13796 in disp-step-syscall.exp
Date: Thu, 18 Feb 2016 12:00:00 -0000 [thread overview]
Message-ID: <1455796823-18128-1-git-send-email-yao.qi@linaro.org> (raw)
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.
---
gdb/testsuite/gdb.base/disp-step-syscall.exp | 6 ------
1 file changed, 6 deletions(-)
diff --git a/gdb/testsuite/gdb.base/disp-step-syscall.exp b/gdb/testsuite/gdb.base/disp-step-syscall.exp
index 7426ee7..80cdc3b 100644
--- a/gdb/testsuite/gdb.base/disp-step-syscall.exp
+++ b/gdb/testsuite/gdb.base/disp-step-syscall.exp
@@ -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
}
--
1.9.1
next reply other threads:[~2016-02-18 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 12:00 Yao Qi [this message]
2016-02-18 12:06 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1455796823-18128-1-git-send-email-yao.qi@linaro.org \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox