From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5 V3] target-assisted range stepping
Date: Tue, 14 May 2013 19:10:00 -0000 [thread overview]
Message-ID: <20130514191026.13213.39574.stgit@brno.lan> (raw)
It took a while, but finally here's my take on the range stepping
series. This is based on Yao's v1 and v2 series, so I'm calling it
v3. The gist of the feature is the same, although the implementation
in both GDB and GDBserver is a different.
v2 was here:
<http://sourceware.org/ml/gdb-patches/2013-04/msg00284.html>
The docs/NEWS/help bits have changed, so they'll need another review.
Tested with native GDB and GDBserver on x86_64 Fedora 17.
Series also available here for convenience:
https://github.com/palves/gdb/tree/range-stepping-v3
https://github.com/palves/gdb.git range-stepping-v3
Please let me know what you think.
Apologies for taking so long in getting this through... :-(
---
Pedro Alves (5):
Factor out in-stepping-range checks.
Convert rs->support_vCont_t to a struct
range stepping: gdb
range stepping: gdbserver (x86 GNU/Linux)
range stepping: tests
gdb/NEWS | 22 ++
gdb/doc/gdb.texinfo | 49 +++++
gdb/gdbserver/linux-low.c | 63 ++++++-
gdb/gdbserver/linux-low.h | 8 +
gdb/gdbserver/linux-x86-low.c | 7 +
gdb/gdbserver/server.c | 24 +++
gdb/gdbserver/target.h | 18 ++
gdb/gdbthread.h | 11 +
gdb/infcmd.c | 8 +
gdb/infrun.c | 39 ++++
gdb/remote.c | 119 +++++++++++++
gdb/testsuite/gdb.base/range-stepping.c | 103 +++++++++++
gdb/testsuite/gdb.base/range-stepping.exp | 237 ++++++++++++++++++++++++++
gdb/testsuite/gdb.trace/range-stepping.c | 56 ++++++
gdb/testsuite/gdb.trace/range-stepping.exp | 85 +++++++++
gdb/testsuite/lib/range-stepping-support.exp | 50 +++++
gdb/thread.c | 7 +
17 files changed, 884 insertions(+), 22 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/range-stepping.c
create mode 100644 gdb/testsuite/gdb.base/range-stepping.exp
create mode 100644 gdb/testsuite/gdb.trace/range-stepping.c
create mode 100644 gdb/testsuite/gdb.trace/range-stepping.exp
create mode 100644 gdb/testsuite/lib/range-stepping-support.exp
--
Pedro Alves
next reply other threads:[~2013-05-14 19:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 19:10 Pedro Alves [this message]
2013-05-14 19:10 ` [PATCH 3/5] range stepping: gdb Pedro Alves
2013-05-14 19:46 ` Eli Zaretskii
2013-05-15 10:23 ` Pedro Alves
2013-05-15 11:22 ` Eli Zaretskii
2013-05-15 12:39 ` Pedro Alves
2013-05-15 13:46 ` Eli Zaretskii
2013-05-15 13:58 ` Pedro Alves
2013-05-15 18:20 ` Pedro Alves
2013-05-16 6:08 ` Eli Zaretskii
2013-05-20 18:43 ` Pedro Alves
2013-05-20 19:05 ` Eli Zaretskii
2013-05-23 0:47 ` Yao Qi
2013-05-23 17:22 ` Pedro Alves
2013-05-14 19:10 ` [PATCH 1/5] Factor out in-stepping-range checks Pedro Alves
2013-05-14 19:37 ` Tom Tromey
2013-05-14 19:10 ` [PATCH 2/5] Convert rs->support_vCont_t to a struct Pedro Alves
2013-05-14 19:40 ` Tom Tromey
2013-05-14 19:10 ` [PATCH 4/5] range stepping: gdbserver (x86 GNU/Linux) Pedro Alves
2013-05-14 19:47 ` Eli Zaretskii
2013-05-14 20:14 ` Tom Tromey
2013-05-23 17:44 ` Pedro Alves
2013-05-24 11:33 ` Pedro Alves
2013-05-15 12:14 ` Yao Qi
2013-05-20 18:01 ` Pedro Alves
2013-05-23 0:56 ` Yao Qi
2013-05-23 17:26 ` Pedro Alves
2013-05-14 19:11 ` [PATCH 5/5] range stepping: tests Pedro Alves
2013-05-22 14:32 ` Yao Qi
2013-05-23 17:34 ` Pedro Alves
2013-05-23 18:03 ` Pedro Alves
2013-05-24 2:27 ` Yao Qi
2013-05-24 9:45 ` Pedro Alves
2013-05-24 9:57 ` Yao Qi
2013-05-14 20:21 ` [PATCH 0/5 V3] target-assisted range stepping Tom Tromey
2013-05-23 17:44 ` Pedro Alves
2013-05-23 1:02 ` Yao Qi
2013-05-23 17:46 ` 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=20130514191026.13213.39574.stgit@brno.lan \
--to=palves@redhat.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