From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/6] Fix a bunch of run control bugs.
Date: Tue, 25 Feb 2014 20:32:00 -0000 [thread overview]
Message-ID: <1393360363-5603-1-git-send-email-palves@redhat.com> (raw)
I started out by doing a couple tweaks to
signal-while-stepping-over-bp-other-thread.exp, to make it run against
remote targets too, and then that didn't work, because of some bug.
And then fixing that bug required fixing some other bug, and ...
Well, this is the result. This changes heavily core run control code,
which affects software single-step targets too. For more comfortable
development and testing, I actually hacked on this against my software
single-step on x86 branch first.
Pedro Alves (6):
PR gdb/16575: stale breakpoint instructions in the code cache
PR breakpoints/7143 - Watchpoint does not trigger when first set
Fix missing breakpoing/watchpoint hits, eliminate deferred_step_ptid.
Fix for even more missed events; eliminate thread-hop code.
Handle multiple step-overs.
Make signal-while-stepping-over-bp-other-thread.exp run against
remote targets too.
gdb/breakpoint.c | 210 ++++--
gdb/breakpoint.h | 10 +
gdb/dcache.c | 100 ++-
gdb/dcache.h | 15 +-
gdb/inferior.h | 6 +
gdb/infrun.c | 716 +++++++++------------
gdb/target.c | 53 +-
gdb/testsuite/gdb.base/breakpoint-shadow.exp | 38 +-
gdb/testsuite/gdb.base/watchpoint.exp | 13 +-
gdb/testsuite/gdb.cp/annota2.exp | 3 -
gdb/testsuite/gdb.cp/annota3.exp | 3 -
gdb/testsuite/gdb.threads/multiple-step-overs.c | 105 +++
gdb/testsuite/gdb.threads/multiple-step-overs.exp | 80 +++
.../signal-while-stepping-over-bp-other-thread.c | 2 +
.../signal-while-stepping-over-bp-other-thread.exp | 16 +-
.../gdb.threads/step-over-lands-on-breakpoint.c | 65 ++
.../gdb.threads/step-over-lands-on-breakpoint.exp | 64 ++
.../gdb.threads/step-over-trips-on-watchpoint.c | 65 ++
.../gdb.threads/step-over-trips-on-watchpoint.exp | 70 ++
19 files changed, 1039 insertions(+), 595 deletions(-)
create mode 100644 gdb/testsuite/gdb.threads/multiple-step-overs.c
create mode 100644 gdb/testsuite/gdb.threads/multiple-step-overs.exp
create mode 100644 gdb/testsuite/gdb.threads/step-over-lands-on-breakpoint.c
create mode 100644 gdb/testsuite/gdb.threads/step-over-lands-on-breakpoint.exp
create mode 100644 gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c
create mode 100644 gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.exp
--
1.7.11.7
next reply other threads:[~2014-02-25 20:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 20:32 Pedro Alves [this message]
2014-02-25 20:32 ` [PATCH 3/6] Fix missing breakpoing/watchpoint hits, eliminate deferred_step_ptid Pedro Alves
2014-03-04 6:05 ` Yao Qi
2014-03-05 16:10 ` Pedro Alves
2014-02-25 20:32 ` [PATCH 1/6] PR gdb/16575: stale breakpoint instructions in the code cache Pedro Alves
2014-03-04 4:02 ` Yao Qi
2014-03-05 15:13 ` Pedro Alves
2014-03-05 15:14 ` Pedro Alves
2014-02-25 20:32 ` [PATCH 2/6] PR breakpoints/7143 - Watchpoint does not trigger when first set Pedro Alves
2014-03-05 15:35 ` Pedro Alves
2014-02-25 20:33 ` [PATCH 4/6] Fix for even more missed events; eliminate thread-hop code Pedro Alves
2014-03-05 15:45 ` Pedro Alves
2014-02-25 20:33 ` [PATCH 5/6] Handle multiple step-overs Pedro Alves
2014-02-25 21:08 ` [PATCH 6/6] Make signal-while-stepping-over-bp-other-thread.exp run against remote targets too Pedro Alves
2014-02-26 13:36 ` [PATCH 3.5/6] Multiple Ada task-specific breakpoints at the same address Pedro Alves
2014-02-26 14:19 ` Joel Brobecker
2014-02-26 14:27 ` 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=1393360363-5603-1-git-send-email-palves@redhat.com \
--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