From: Simon Marchi <simark@simark.ca>
To: Kamil Rytarowski <n54@gmx.com>,
gdb-patches@sourceware.org, jhb@FreeBSD.org
Subject: Re: [PATCH v3] Implement xfer_partial TARGET_OBJECT_SIGNAL_INFO for NetBSD
Date: Tue, 28 Jul 2020 12:21:56 -0400 [thread overview]
Message-ID: <01964ed7-b2cd-5e0c-0630-b2324503d694@simark.ca> (raw)
In-Reply-To: <20200728155844.6609-1-n54@gmx.com>
On 2020-07-28 11:58 a.m., Kamil Rytarowski wrote:
> NetBSD implements reading and overwriting siginfo_t received by the
> tracee. With TARGET_OBJECT_SIGNAL_INFO signal information can be
> examined and modified through the special variable $_siginfo.
>
> Implement the "get_siginfo_type" gdbarch method for NetBSD architectures.
>
> As with Linux architectures, cache the created type in the gdbarch when it
> is first created. Currently NetBSD uses an identical siginfo type on
> all architectures, so there is no support for architecture-specific fields.
>
> gdb/ChangeLog:
>
> * nbsd-nat.h (nbsd_nat_target::xfer_partial): New declaration.
> * nbsd-nat.c (nbsd_nat_target::xfer_partial): New function.
> * nbsd-tdep.c (nbsd_gdbarch_data_handle, struct nbsd_gdbarch_data)
> (init_nbsd_gdbarch_data, get_nbsd_gdbarch_data)
> (nbsd_get_siginfo_type): New.
> (nbsd_init_abi): Install gdbarch "get_siginfo_type" method.
> (_initialize_nbsd_tdep): New
> ---
Thanks, this is OK.
Simon
prev parent reply other threads:[~2020-07-28 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 7:41 [PATCH] " Kamil Rytarowski
2020-07-27 15:42 ` John Baldwin
2020-07-28 13:26 ` Simon Marchi
2020-07-28 15:07 ` Kamil Rytarowski
2020-07-28 15:15 ` Simon Marchi
2020-07-28 15:17 ` Kamil Rytarowski
2020-07-28 15:21 ` Simon Marchi
2020-07-28 15:04 ` [PATCH v2] " Kamil Rytarowski
2020-07-28 15:17 ` Simon Marchi
2020-07-28 15:58 ` [PATCH v3] " Kamil Rytarowski
2020-07-28 16:21 ` Simon Marchi [this message]
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=01964ed7-b2cd-5e0c-0630-b2324503d694@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=n54@gmx.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