From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/9] software single-step support rework, fix limitations
Date: Fri, 26 Sep 2014 00:39:00 -0000 [thread overview]
Message-ID: <1411691982-10744-1-git-send-email-palves@redhat.com> (raw)
This series reworks software single-step support. In a nutshell:
- Makes single-step breakpoints regular breakpoints and puts them on
the global location chain.
- Makes the moribund location machinery aware of software single-step
breakpoints.
- Removes the currently limitation that only 2 single-step breakpoints
can be inserted. Some archs, like PPC, need this.
- Makes software single-step work when stepping through read-only code
regions.
- Adds support for having multiple threads software single-stepping
simultaneously. Currently, in non-stop, all single-step requests
are handled by displaced stepping the threads, which means threads
are serialized, because only one thread can be displaced stepping at
any given time.
- Finally eliminates deprecated_insert_raw_breakpoint and friends.
- Removes a set of run control globals along the way.
- And cleans things up here and there.
Tested on:
- x86_64 Fedora 20
- x86_64 Fedora 20 w/ 'software single-step on x86' series
- PPC64 Fedora 18
Pedro Alves (9):
Decide whether we may have removed breakpoints based on step_over_info
Rewrite non-continuable watchpoints handling
Put single-step breakpoints on the bp_location chain
Remove deprecated_insert_raw_breakpoint and friends
Switch back to stepped thread: clear step-over info
thread.c: cleanup breakpoint deletion
infrun.c: add for_each_just_stopped_thread
Make single-step breakpoints be per-thread
Non-stop + software single-step archs: don't force displaced-stepping
for all single-steps
gdb/breakpoint.c | 402 +++++++++++++-----------------------------------------
gdb/breakpoint.h | 31 ++---
gdb/gdbthread.h | 25 ++++
gdb/infrun.c | 360 ++++++++++++++++++++++--------------------------
gdb/infrun.h | 4 +
gdb/record-full.c | 8 +-
gdb/thread.c | 80 ++++++++---
7 files changed, 364 insertions(+), 546 deletions(-)
--
1.9.3
next reply other threads:[~2014-09-26 0:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 0:39 Pedro Alves [this message]
2014-09-26 0:39 ` [PATCH 2/9] Rewrite non-continuable watchpoints handling Pedro Alves
2014-09-26 0:39 ` [PATCH 1/9] Decide whether we may have removed breakpoints based on step_over_info Pedro Alves
2014-09-28 12:52 ` Yao Qi
2014-10-02 18:05 ` Pedro Alves
2014-10-06 1:06 ` Yao Qi
2014-10-06 8:42 ` Pedro Alves
2014-09-26 0:40 ` [PATCH 3/9] Put single-step breakpoints on the bp_location chain Pedro Alves
2014-09-28 12:36 ` Yao Qi
2014-09-30 13:01 ` Pedro Alves
2014-09-30 13:15 ` Pedro Alves
2014-09-29 6:33 ` Yao Qi
2014-10-02 17:55 ` Pedro Alves
2014-09-26 0:40 ` [PATCH 5/9] Switch back to stepped thread: clear step-over info Pedro Alves
2014-09-30 16:33 ` Pedro Alves
2014-09-26 0:40 ` [PATCH 8/9] Make single-step breakpoints be per-thread Pedro Alves
2014-09-26 0:40 ` [PATCH 9/9] Non-stop + software single-step archs: don't force displaced-stepping for all single-steps Pedro Alves
2014-09-26 0:40 ` [PATCH 4/9] Remove deprecated_insert_raw_breakpoint and friends Pedro Alves
2014-09-26 1:18 ` [PATCH 6/9] thread.c: cleanup breakpoint deletion Pedro Alves
2014-09-26 1:36 ` [PATCH 7/9] infrun.c: add for_each_just_stopped_thread 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=1411691982-10744-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).