public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Improve target.h & target_ops & xfer_partial descriptions
Date: Wed, 24 Apr 2024 22:49:57 -0400	[thread overview]
Message-ID: <94e85836-87f1-4185-a321-273a8c1fa32d@simark.ca> (raw)
In-Reply-To: <20240424144647.2849085-1-pedro@palves.net>



On 2024-04-24 10:46, Pedro Alves wrote:
> Working backwards in terms of motivation for the patch:
> 
> - When accessing memory via the xfer_partial interface, the process
>   that we're accessing is indicated by inferior_ptid.  This can be
>   either the same process as current inferior, or a fork child which
>   does not exist in the inferior list.  This is not documented
>   currently.  This commit fixes that.
> 
> - For target deletation to work, we must always make the inferior we
>   want to call the target method on, the current inferior.  This
>   wasn't documented, AFAICT, so this commit fixes that too.  I put
>   that in the intro comment to target_ops.
> 
> - I actually started writing a larger intro comment to target_ops, as
>   there was seemingly none, which I did find odd.  However, I then
>   noticed the description closer to the top of the file.  I missed it
>   the first time, because for some reason, that intro comment is no
>   longer at the top of the file, as #includes etc. have been added
>   above it over the years.  This commit fixes that too, by moving that
>   intro comment to the top.
> 
> Change-Id: Id21f5462947f2a0f6f3ac0c42532df62ba355914

Thanks, this LGTM.

Approved-By: Simon Marchi <simon.marchi@efficios.com>

Simon

  reply	other threads:[~2024-04-25  2:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 14:46 Pedro Alves
2024-04-25  2:49 ` Simon Marchi [this message]
2024-04-25 14:00 ` Tom Tromey
2024-04-26 21:08   ` 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=94e85836-87f1-4185-a321-273a8c1fa32d@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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).