Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/7 V2] Leave child suspended when step over parent
Date: Fri, 26 Feb 2016 14:03:00 -0000	[thread overview]
Message-ID: <1456495426-7520-1-git-send-email-yao.qi@linaro.org> (raw)
In-Reply-To: <1455892594-2294-1-git-send-email-yao.qi@linaro.org>

Hi,
Here is the v2 of this patch series.  V1 can be found
https://sourceware.org/ml/gdb-patches/2016-02/msg00591.html

The changes in v2 are:

 1. Remove patch "Use loop in disp-step-fork.c and disp-step-vfork.c"
    from this series,
 2. Open PR server/19736 for the bug this series fixes, and mention
    this PR in the comments of tests,
 3. Restart GDB in each test instead of doing multiple tests in a
    single debugging session,
 4. Fix some wording issues in the comments.
 5. Use foreach_with_prefix,

*** BLURB HERE ***

Yao Qi (7):
  [GDBserver] Leave child suspended when step over parent
  Refactor gdb.base/disp-step-syscall.exp for general step over test
  Step over syscalll insn with disp-step on and off
  Step over fork/vfork syscall insn in gdbserver
  Rename disp-step-syscall.exp to step-over-syscall.exp
  Reformat gdb.base/step-over-syscall.exp
  New test about step over clone syscall

 gdb/gdbserver/linux-low.c                          |  16 +-
 gdb/testsuite/gdb.base/disp-step-syscall.exp       | 154 -------------
 gdb/testsuite/gdb.base/step-over-clone.c           |  54 +++++
 .../{disp-step-fork.c => step-over-fork.c}         |   0
 gdb/testsuite/gdb.base/step-over-syscall.exp       | 249 +++++++++++++++++++++
 .../{disp-step-vfork.c => step-over-vfork.c}       |   0
 6 files changed, 314 insertions(+), 159 deletions(-)
 delete mode 100644 gdb/testsuite/gdb.base/disp-step-syscall.exp
 create mode 100644 gdb/testsuite/gdb.base/step-over-clone.c
 rename gdb/testsuite/gdb.base/{disp-step-fork.c => step-over-fork.c} (100%)
 create mode 100644 gdb/testsuite/gdb.base/step-over-syscall.exp
 rename gdb/testsuite/gdb.base/{disp-step-vfork.c => step-over-vfork.c} (100%)

-- 
1.9.1


  parent reply	other threads:[~2016-02-26 14:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 14:36 [PATCH 0/8] " Yao Qi
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: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: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-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 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-26 14:03 ` Yao Qi [this message]
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   ` [PATCH 5/7] Rename disp-step-syscall.exp to step-over-syscall.exp 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 1/7] [GDBserver] Leave child suspended when step over parent 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 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 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-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