From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: gdb-patches@sourceware.org
Cc: uweigand@de.ibm.com
Subject: [PATCH 0/3] low_new_clone in linux-nat.c and powerpc watchpoint fixes
Date: Fri, 26 Jul 2019 12:50:00 -0000 [thread overview]
Message-ID: <20190726125012.6503-1-pedromfc@linux.ibm.com> (raw)
This patch series fixes some issues with hardware breakpoints and
watchpoints in the powerpc linux native target.
The first patch adds a new "low" method to linux-nat.c, which is needed
in ppc-linux-nat.c. The second one is a small refactoring, and the third
one is the fix itself.
Pedro Franco de Carvalho (3):
Add low_new_clone method to linux_nat_target.
[PowerPC] Move up some register access routines
[PowerPC] Fix debug register issues in ppc-linux-nat
gdb/linux-nat.c | 4 +
gdb/linux-nat.h | 4 +
gdb/ppc-linux-nat.c | 1561 ++++++++++++++++++++++++++++---------------
3 files changed, 1041 insertions(+), 528 deletions(-)
--
2.20.1
next reply other threads:[~2019-07-26 12:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 12:50 Pedro Franco de Carvalho [this message]
2019-07-26 12:50 ` [PATCH 2/3] [PowerPC] Move up some register access routines Pedro Franco de Carvalho
2019-08-08 16:25 ` Ulrich Weigand
2019-07-26 12:50 ` [PATCH 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat Pedro Franco de Carvalho
2019-08-08 16:24 ` Ulrich Weigand
2019-08-08 20:27 ` Pedro Franco de Carvalho
2019-08-09 11:04 ` Ulrich Weigand
2019-08-09 15:04 ` Pedro Franco de Carvalho
2019-08-09 15:28 ` Ulrich Weigand
2019-08-09 15:53 ` Pedro Franco de Carvalho
2019-08-13 13:50 ` Pedro Franco de Carvalho
2019-08-21 15:31 ` Ulrich Weigand
2019-08-21 17:45 ` Pedro Franco de Carvalho
2019-08-22 10:27 ` Ulrich Weigand
2019-07-26 12:50 ` [PATCH 1/3] Add low_new_clone method to linux_nat_target Pedro Franco de Carvalho
2019-08-08 14:05 ` Ulrich Weigand
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=20190726125012.6503-1-pedromfc@linux.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.com \
/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).