From: Pedro Alves <palves@redhat.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] windows-nat.c: Don't install a deprecated_xfer_memory method.
Date: Mon, 26 Aug 2013 16:54:00 -0000 [thread overview]
Message-ID: <521B8836.3030307@redhat.com> (raw)
In-Reply-To: <521B87D8.1040303@redhat.com>
On 08/26/2013 05:52 PM, Pedro Alves wrote:
> On 08/23/2013 10:36 PM, Pierre Muller wrote:
>> Hi Pedro,
>>
>> I think that your patch can be further enhanced by this change:
>> ReadProcessMemory and WriteProcessMemory
>> function both fail and report ERROR_PARTIAL_COPY
>> in GetLastError
>> if only a part of the requested memory was read/written.
>
> Interesting. It does sound like a good idea.
>
> However, could you send that as a separate patch, please?
And I meant to add for forgot -- that separate patch could
then also propose the same change for gdbserver too. :-)
> Otherwise, the single combined patch can potentially cause issues
> due to two logically unrelated changes: potential problems caused by
> not installing deprecated_xfer_memory anymore, and instead going
> through xfer_partial directly; and then potential problems due to
> that change. Keeping the patches separate allows for better
> bisecting for what might have caused a regression.
--
Pedro Alves
next prev parent reply other threads:[~2013-08-26 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 18:12 Pedro Alves
2013-08-23 20:08 ` Joel Brobecker
2013-08-27 11:38 ` Pedro Alves
2013-08-23 21:37 ` Pierre Muller
2013-08-26 16:52 ` Pedro Alves
2013-08-26 16:54 ` Pedro Alves [this message]
2013-08-27 0:50 ` Yao Qi
2013-08-27 11:37 ` 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=521B8836.3030307@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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