From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: gdb-patches@sourceware.org
Cc: ulrich.weigand@de.ibm.com, rcardoso@linux.ibm.com
Subject: [PATCH v2 0/3] low_new_clone in linux-nat.c and powerpc watchpoint fixes
Date: Fri, 14 Feb 2020 20:55:00 -0000 [thread overview]
Message-ID: <20200214205443.1073579-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.
The differences compared to v1 are:
* Changed the stopped_data_addres/stopped_by_watchpoint so the low_*
versions so that we get the right stop_reason in the stop_reason field
of lwp_info. We can then use stop_reason in low_prepare_to_resume as
an additional indicator that the debug registers are stale, since some
kernel configurations disable a watchpoint after a hit.
* Instead of using an observer callback to clean-up the thread state, I
did this in low_delete_thread, because I'm more confident that this
will be called (some lwp_info object might not end up having an
associated GDB thread object).
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 | 1584 ++++++++++++++++++++++++++++---------------
3 files changed, 1058 insertions(+), 534 deletions(-)
--
2.24.1
next reply other threads:[~2020-02-14 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 20:55 Pedro Franco de Carvalho [this message]
2020-02-14 20:55 ` [PATCH v2 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat Pedro Franco de Carvalho
2020-02-17 17:47 ` Ulrich Weigand
2020-02-18 20:31 ` Pedro Franco de Carvalho
2020-02-19 13:46 ` Ulrich Weigand
2020-03-13 20:19 ` Pedro Franco de Carvalho
2020-03-27 18:50 ` Pedro Franco de Carvalho
2020-03-27 18:54 ` [PATCH] " Pedro Franco de Carvalho
2020-03-30 13:04 ` Ulrich Weigand
2020-03-30 13:03 ` [PATCH v2 3/3] " Ulrich Weigand
2020-03-30 15:13 ` Pedro Franco de Carvalho
2020-02-14 20:55 ` [PATCH v2 2/3] [PowerPC] Move up some register access routines Pedro Franco de Carvalho
2020-02-17 17:48 ` Ulrich Weigand
2020-02-14 20:55 ` [PATCH v2 1/3] Add low_new_clone method to linux_nat_target Pedro Franco de Carvalho
2020-02-17 17:49 ` 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=20200214205443.1073579-1-pedromfc@linux.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=rcardoso@linux.ibm.com \
--cc=ulrich.weigand@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).