From: Simon Marchi <simark@simark.ca>
To: John Baldwin <jhb@FreeBSD.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/5] fbsd-nat: Use regset supply/collect methods.
Date: Tue, 22 Nov 2022 15:20:04 -0500 [thread overview]
Message-ID: <6383b8c6-c620-5b14-bd48-a53103d383d6@simark.ca> (raw)
In-Reply-To: <20220708005816.9408-3-jhb@FreeBSD.org>
On 7/7/22 20:58, John Baldwin wrote:
> fbsd-nat includes various helper routines for fetching and storing
> register sets via ptrace where the register set is described by a
> regset. These helper routines directly invoke the
> supply/collect_regset regcache methods which doesn't permit a regset
> to provide custom logic when fetching or storing a register set.
> Instead, just use the function pointers from the struct regset
> directly.
> ---
> gdb/fbsd-nat.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/gdb/fbsd-nat.c b/gdb/fbsd-nat.c
> index 281b034b115..9d7383ac0ab 100644
> --- a/gdb/fbsd-nat.c
> +++ b/gdb/fbsd-nat.c
> @@ -1744,7 +1744,7 @@ fbsd_nat_target::fetch_register_set (struct regcache *regcache, int regnum,
> if (ptrace (fetch_op, pid, (PTRACE_TYPE_ARG3) regs, 0) == -1)
> perror_with_name (_("Couldn't get registers"));
>
> - regcache->supply_regset (regset, regnum, regs, size);
> + regset->supply_regset (regset, regcache, regnum, regs, size);
> return true;
> }
> return false;
> @@ -1768,7 +1768,7 @@ fbsd_nat_target::store_register_set (struct regcache *regcache, int regnum,
> if (ptrace (fetch_op, pid, (PTRACE_TYPE_ARG3) regs, 0) == -1)
> perror_with_name (_("Couldn't get registers"));
>
> - regcache->collect_regset (regset, regnum, regs, size);
> + regset->collect_regset (regset, regcache, regnum, regs, size);
>
> if (ptrace (store_op, pid, (PTRACE_TYPE_ARG3) regs, 0) == -1)
> perror_with_name (_("Couldn't write registers"));
> @@ -1813,7 +1813,7 @@ fbsd_nat_target::fetch_regset (struct regcache *regcache, int regnum, int note,
> if (ptrace (PT_GETREGSET, pid, (PTRACE_TYPE_ARG3) &iov, note) == -1)
> perror_with_name (_("Couldn't get registers"));
>
> - regcache->supply_regset (regset, regnum, regs, size);
> + regset->supply_regset (regset, regcache, regnum, regs, size);
> return true;
> }
> return false;
> @@ -1838,7 +1838,7 @@ fbsd_nat_target::store_regset (struct regcache *regcache, int regnum, int note,
> if (ptrace (PT_GETREGSET, pid, (PTRACE_TYPE_ARG3) &iov, note) == -1)
> perror_with_name (_("Couldn't get registers"));
>
> - regcache->collect_regset (regset, regnum, regs, size);
> + regset->collect_regset (regset, regcache, regnum, regs, size);
>
> if (ptrace (PT_SETREGSET, pid, (PTRACE_TYPE_ARG3) &iov, note) == -1)
> perror_with_name (_("Couldn't write registers"));
> --
> 2.36.1
>
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Simon
next prev parent reply other threads:[~2022-11-22 20:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 0:58 [PATCH 0/5] Improve support for regcache_map_entry with variable register base John Baldwin
2022-07-08 0:58 ` [PATCH 1/5] regcache: Add collect/supply_regset variants that accept a " John Baldwin
2022-11-22 19:56 ` Simon Marchi
2022-11-22 20:18 ` Simon Marchi
2022-11-22 22:32 ` John Baldwin
2022-07-08 0:58 ` [PATCH 2/5] fbsd-nat: Use regset supply/collect methods John Baldwin
2022-11-22 20:20 ` Simon Marchi [this message]
2022-07-08 0:58 ` [PATCH 3/5] fbsd-nat: Pass an optional register base to the register set helpers John Baldwin
2022-11-22 20:38 ` Simon Marchi
2022-11-22 22:16 ` John Baldwin
2022-11-22 22:25 ` John Baldwin
2022-07-08 0:58 ` [PATCH 4/5] arm-fbsd: Use a static regset for the TLS register set John Baldwin
2022-11-22 20:39 ` Simon Marchi
2022-07-08 0:58 ` [PATCH 5/5] aarch64-fbsd: " John Baldwin
2022-11-22 20:40 ` Simon Marchi
2022-07-21 14:53 ` [PATCH 0/5] Improve support for regcache_map_entry with variable register base John Baldwin
2022-08-22 18:11 ` [PING] " John Baldwin
2022-09-20 17:50 ` John Baldwin
2022-10-20 20:26 ` [PING 4] " John Baldwin
2022-11-21 18:21 ` [PING 5] " John Baldwin
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=6383b8c6-c620-5b14-bd48-a53103d383d6@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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).