From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Remove lwp -> pid conversion in linux_nat_xfer_partial
Date: Wed, 22 Mar 2017 11:28:00 -0000 [thread overview]
Message-ID: <0ebe5a99-919e-cfe6-d6c6-d00ef0fa9f8f@redhat.com> (raw)
In-Reply-To: <20170322030215.27737-1-simon.marchi@polymtl.ca>
On 03/22/2017 03:02 AM, Simon Marchi wrote:
> New in v2:
>
> - Use lwp in linux_proc_xfer_partial and linux_proc_xfer_spu.
> - Updated commit message (stole some of Pedro's text)
Thanks!
> - if the leader exits, and goes zombie, then several files under
> "/proc/<pid>" won't work, though using "/proc/<pid>/task/<tid>" would.
> The latter path form is also generally better for being robust in
> the case TID exits and is reused in another process, much like
> tkill vs tgkill.
The part about TID-reuse robustness actually doesn't make sense here
yet, though, since this patch is not switching to "/proc/<pid>/task/<tid>".
So reduce that to:
- if the leader (<pid>) had exited and is thus now zombie, then several
files under "/proc/<pid>" won't work, while they will if you use
"/proc/<lwp>".
Otherwise LGTM.
Thanks,
Pedro Alves
prev parent reply other threads:[~2017-03-22 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 22:18 [PATCH] " Simon Marchi
2017-03-21 23:58 ` Pedro Alves
2017-03-22 0:42 ` Simon Marchi
2017-03-22 1:01 ` Pedro Alves
2017-03-22 1:13 ` Pedro Alves
2017-03-22 1:22 ` Simon Marchi
2017-03-22 3:03 ` [PATCH v2] " Simon Marchi
2017-03-22 11:28 ` Pedro Alves [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=0ebe5a99-919e-cfe6-d6c6-d00ef0fa9f8f@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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