From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4 3/4] gdbserver: Support read-only regsets in linux-low.c
Date: Fri, 12 Dec 2014 12:21:00 -0000 [thread overview]
Message-ID: <548ADDAC.7010500@redhat.com> (raw)
In-Reply-To: <1418379431-14407-4-git-send-email-arnez@linux.vnet.ibm.com>
On 12/12/2014 10:16 AM, Andreas Arnez wrote:
> For GNU/Linux targets using the regsets interface, this change
> supports regsets that can be read but not written. The S390 "last
> break" regset is an example. So far it had been defined with
> regset->set_request == PTRACE_GETREGSET, such that the respective
> ptrace call does not cause any harm. Now we just skip the whole
> read/modify/write sequence for regsets that do not define a
> fill_function.
Looks good to me.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-12-12 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 10:17 [PATCH v4 0/4] gdbserver: Fix support for S390 TDB Andreas Arnez
2014-12-12 10:17 ` [PATCH v4 1/4] gdbserver: Rephrase loops in regsets_fetch/store_inferior_registers Andreas Arnez
2014-12-12 12:04 ` Pedro Alves
2014-12-12 10:18 ` [PATCH v4 2/4] gdbserver: Prevent stale/random values in register cache Andreas Arnez
2014-12-12 12:14 ` Pedro Alves
2014-12-12 10:18 ` [PATCH v4 3/4] gdbserver: Support read-only regsets in linux-low.c Andreas Arnez
2014-12-12 12:21 ` Pedro Alves [this message]
2014-12-12 10:19 ` [PATCH v4 4/4] S390: Fix gdbserver support for TDB Andreas Arnez
2014-12-12 12:23 ` 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=548ADDAC.7010500@redhat.com \
--to=palves@redhat.com \
--cc=arnez@linux.vnet.ibm.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