From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 00/12 V2] Use reinsert breakpoint for vCont;s
Date: Thu, 02 Jun 2016 09:31:00 -0000 [thread overview]
Message-ID: <1464859846-15619-1-git-send-email-yao.qi@linaro.org> (raw)
Here is the V2 of this patch series, V1 can be found
https://sourceware.org/ml/gdb-patches/2016-05/msg00358.html
Nowadays, reinsert breakpoint is used in GDBserver to step over a
breakpoint. I want to use it to handle vCont;s too. The idea is that
when GDBserver receives resume_step request from GDB, use the software
single step logic, insert reinsert_breakpoint on the next pcs, and
resume the thread. This means we have multiple reinsert_breakpoints
for different threads for either step-over or vCont;s.
Patches 2~5 are the fixes to existing GDBserver problems on step-over
with reinsert_breakpoint in various cases (exit, fork, and vfork).
Although these 4 patches can be sent as another patch series, I still
include them in this series, as they are derived from the V1 review.
Patches 7 and 12 aren't changed. All review comments are addressed
in the rest of patches. Once this series goes in, I'll start to rename
'reinsert_breakpoint' and 'other_breakpoint' to match their usages in
GDBserver.
Regression tested on {x86_64, arm, aarch64}-linux.
*** BLURB HERE ***
Yao Qi (12):
Switch to current thread in finish_step_over
More assert checks on reinsert breakpoint
Step over exit with reinsert breakpoints
Delete reinsert breakpoints from forked child
Handle reinsert breakpoints for vforked child
Pass breakpoint type in set_breakpoint_at
Create sub classes of 'struct breakpoint'
Refactor clone_all_breakpoints
Make reinsert_breakpoint thread specific
Switch current_thread to lwp's thread in
install_software_single_step_breakpoints
Use reinsert_breakpoint for vCont;s
Support vCont s and S actions with software single step
gdb/gdbserver/gdbthread.h | 3 +
gdb/gdbserver/inferiors.c | 12 +
gdb/gdbserver/linux-low.c | 206 +++++++++++++++--
gdb/gdbserver/mem-break.c | 341 +++++++++++++++++++++-------
gdb/gdbserver/mem-break.h | 44 ++--
gdb/gdbserver/server.c | 17 +-
gdb/testsuite/gdb.base/step-over-exit.c | 50 ++++
gdb/testsuite/gdb.base/step-over-exit.exp | 127 +++++++++++
gdb/testsuite/gdb.base/step-over-fork-1.c | 51 +++++
gdb/testsuite/gdb.base/step-over-fork-1.exp | 106 +++++++++
10 files changed, 842 insertions(+), 115 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/step-over-exit.c
create mode 100644 gdb/testsuite/gdb.base/step-over-exit.exp
create mode 100644 gdb/testsuite/gdb.base/step-over-fork-1.c
create mode 100644 gdb/testsuite/gdb.base/step-over-fork-1.exp
--
1.9.1
next reply other threads:[~2016-06-02 9:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 9:31 Yao Qi [this message]
2016-06-02 9:31 ` [PATCH 11/12] Use reinsert_breakpoint " Yao Qi
2016-06-13 15:55 ` Pedro Alves
2016-06-14 13:14 ` Yao Qi
2016-06-14 15:48 ` Pedro Alves
2016-06-15 16:41 ` Yao Qi
2016-06-17 15:10 ` Pedro Alves
2016-06-20 18:09 ` Antoine Tremblay
2016-06-02 9:31 ` [PATCH 04/12] Delete reinsert breakpoints from forked child Yao Qi
2016-06-13 15:02 ` Pedro Alves
2016-06-13 16:53 ` Yao Qi
2016-06-13 17:29 ` Pedro Alves
2016-06-14 11:17 ` Yao Qi
2016-06-14 11:40 ` Pedro Alves
2016-06-17 9:53 ` Yao Qi
2016-06-02 9:31 ` [PATCH 02/12] More assert checks on reinsert breakpoint Yao Qi
2016-06-13 14:25 ` Pedro Alves
2016-06-02 9:31 ` [PATCH 12/12] Support vCont s and S actions with software single step Yao Qi
2016-06-13 15:56 ` Pedro Alves
2016-06-02 9:31 ` [PATCH 05/12] Handle reinsert breakpoints for vforked child Yao Qi
2016-06-13 15:07 ` Pedro Alves
2016-06-02 9:31 ` [PATCH 10/12] Switch current_thread to lwp's thread in install_software_single_step_breakpoints Yao Qi
2016-06-13 15:26 ` Pedro Alves
2016-06-02 9:31 ` [PATCH 03/12] Step over exit with reinsert breakpoints Yao Qi
2016-06-13 14:37 ` Pedro Alves
2016-06-13 14:52 ` Yao Qi
2016-06-13 15:01 ` Pedro Alves
2016-06-17 9:50 ` Yao Qi
2016-06-02 9:31 ` [PATCH 06/12] Pass breakpoint type in set_breakpoint_at Yao Qi
2016-06-13 15:07 ` Pedro Alves
2016-06-02 9:31 ` [PATCH 07/12] Create sub classes of 'struct breakpoint' Yao Qi
2016-06-13 15:09 ` Pedro Alves
2016-06-02 9:31 ` [PATCH 08/12] Refactor clone_all_breakpoints Yao Qi
2016-06-13 15:14 ` Pedro Alves
2016-06-02 9:31 ` [PATCH 09/12] Make reinsert_breakpoint thread specific Yao Qi
[not found] ` <71a5322e-41e3-9e23-df73-e14b14c1d656@redhat.com>
2016-06-14 12:52 ` Yao Qi
2016-06-14 12:57 ` Pedro Alves
2016-06-02 9:31 ` [PATCH 01/12] Switch to current thread in finish_step_over Yao Qi
2016-06-13 14:25 ` 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=1464859846-15619-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