From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 5/7] Rename disp-step-syscall.exp to step-over-syscall.exp
Date: Fri, 26 Feb 2016 14:04:00 -0000 [thread overview]
Message-ID: <1456495426-7520-6-git-send-email-yao.qi@linaro.org> (raw)
In-Reply-To: <1456495426-7520-1-git-send-email-yao.qi@linaro.org>
disp-step-syscall.exp is extended for stepping over syscall instruction
in different cases, with or without displaced stepping, and stepping
over by GDBserver.
This patch rename disp-step-syscall.exp to step-over-syscall.exp to
reflect this.
gdb/testsuite:
2016-02-26 Yao Qi <yao.qi@linaro.org>
* gdb.base/disp-step-fork.c: Rename to ...
* gdb.base/step-over-fork.c: ... it. New file.
* gdb.base/disp-step-vfork.c: Rename to ...
* gdb.base/step-over-vfork.c: ... it. New file.
* gdb.base/disp-step-syscall.exp: Rename to ...
* gdb.base/step-over-syscall.exp: ... it. New file.
(disp_step_cross_syscall): Rename to ...
(step_over_syscall): ... it.
---
.../gdb.base/{disp-step-fork.c => step-over-fork.c} | 0
.../{disp-step-syscall.exp => step-over-syscall.exp} | 14 +++++++-------
.../gdb.base/{disp-step-vfork.c => step-over-vfork.c} | 0
3 files changed, 7 insertions(+), 7 deletions(-)
rename gdb/testsuite/gdb.base/{disp-step-fork.c => step-over-fork.c} (100%)
rename gdb/testsuite/gdb.base/{disp-step-syscall.exp => step-over-syscall.exp} (96%)
rename gdb/testsuite/gdb.base/{disp-step-vfork.c => step-over-vfork.c} (100%)
diff --git a/gdb/testsuite/gdb.base/disp-step-fork.c b/gdb/testsuite/gdb.base/step-over-fork.c
similarity index 100%
rename from gdb/testsuite/gdb.base/disp-step-fork.c
rename to gdb/testsuite/gdb.base/step-over-fork.c
diff --git a/gdb/testsuite/gdb.base/disp-step-syscall.exp b/gdb/testsuite/gdb.base/step-over-syscall.exp
similarity index 96%
rename from gdb/testsuite/gdb.base/disp-step-syscall.exp
rename to gdb/testsuite/gdb.base/step-over-syscall.exp
index 9ecf2a5..6146f64 100644
--- a/gdb/testsuite/gdb.base/disp-step-syscall.exp
+++ b/gdb/testsuite/gdb.base/step-over-syscall.exp
@@ -47,7 +47,7 @@ proc check_pc_after_cross_syscall { syscall syscall_insn_next_addr } {
proc setup { syscall } {
global gdb_prompt syscall_insn
- set testfile "disp-step-$syscall"
+ set testfile "step-over-$syscall"
clean_restart $testfile
@@ -107,12 +107,12 @@ proc setup { syscall } {
return [list $syscall_insn_addr [get_hexadecimal_valueof "\$pc" "0"]]
}
-proc disp_step_cross_syscall { syscall } {
+proc step_over_syscall { syscall } {
with_test_prefix "$syscall" {
global syscall_insn
global gdb_prompt
- set testfile "disp-step-$syscall"
+ set testfile "step-over-$syscall"
if [build_executable ${testfile}.exp ${testfile} ${testfile}.c {debug}] {
untested ${testfile}.exp
@@ -174,7 +174,7 @@ proc disp_step_cross_syscall { syscall } {
proc break_cond_on_syscall { syscall } {
with_test_prefix "break cond on target : $syscall" {
- set testfile "disp-step-$syscall"
+ set testfile "step-over-$syscall"
set ret [setup $syscall]
@@ -200,10 +200,10 @@ proc break_cond_on_syscall { syscall } {
}
}
-disp_step_cross_syscall "fork"
-disp_step_cross_syscall "vfork"
+step_over_syscall "fork"
+step_over_syscall "vfork"
-set testfile "disp-step-fork"
+set testfile "step-over-fork"
clean_restart $testfile
if { ![runto main] } then {
fail "run to main"
diff --git a/gdb/testsuite/gdb.base/disp-step-vfork.c b/gdb/testsuite/gdb.base/step-over-vfork.c
similarity index 100%
rename from gdb/testsuite/gdb.base/disp-step-vfork.c
rename to gdb/testsuite/gdb.base/step-over-vfork.c
--
1.9.1
next prev parent reply other threads:[~2016-02-26 14:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 14:36 [PATCH 0/8] Leave child suspended when step over parent Yao Qi
2016-02-19 14:36 ` [PATCH 5/8] Step over fork/vfork syscall insn in gdbserver Yao Qi
2016-02-23 20:28 ` Luis Machado
2016-02-25 17:31 ` Pedro Alves
2016-02-19 14:36 ` [PATCH 3/8] Use loop in disp-step-fork.c and disp-step-vfork.c Yao Qi
2016-02-25 17:28 ` Pedro Alves
2016-02-19 14:36 ` [PATCH 4/8] Step over syscalll insn with disp-step on and off Yao Qi
2016-02-25 17:27 ` Pedro Alves
2016-02-19 14:37 ` [PATCH 8/8] New test about step over clone syscall Yao Qi
2016-02-23 20:31 ` Luis Machado
2016-02-25 17:43 ` Pedro Alves
2016-02-25 17:43 ` Pedro Alves
2016-02-19 14:37 ` [PATCH 1/8] [GDBserver] Leave child suspended when step over parent Yao Qi
2016-02-23 20:23 ` Luis Machado
2016-02-25 17:12 ` Pedro Alves
2016-02-19 14:37 ` [PATCH 6/8] Reformat disp-step-syscall.exp Yao Qi
2016-02-19 14:37 ` [PATCH 7/8] Rename disp-step-syscall.exp to step-over-syscall.exp Yao Qi
2016-02-25 17:32 ` Pedro Alves
2016-02-26 14:03 ` [PATCH 0/7 V2] Leave child suspended when step over parent Yao Qi
2016-02-26 14:04 ` [PATCH 3/7] Step over syscalll insn with disp-step on and off Yao Qi
2016-02-26 14:04 ` Yao Qi [this message]
2016-02-26 14:04 ` [PATCH 1/7] [GDBserver] Leave child suspended when step over parent Yao Qi
2016-02-26 14:04 ` [PATCH 7/7] New test about step over clone syscall Yao Qi
2016-02-26 14:04 ` [PATCH 4/7] Step over fork/vfork syscall insn in gdbserver Yao Qi
2016-02-26 15:02 ` Luis Machado
2016-02-26 15:50 ` Yao Qi
2016-02-26 14:04 ` [PATCH 2/7] Refactor gdb.base/disp-step-syscall.exp for general step over test Yao Qi
2016-02-26 14:04 ` [PATCH 6/7] Reformat gdb.base/step-over-syscall.exp Yao Qi
2016-03-03 9:21 ` [PATCH 0/7 V2] Leave child suspended when step over parent Yao Qi
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=1456495426-7520-6-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