From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: asmwarrior <asmwarrior@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [Windows]Fix a bug which cause GDB.exe assert when try to run the inferior
Date: Fri, 21 Feb 2014 10:13:00 -0000 [thread overview]
Message-ID: <530726DB.2000905@redhat.com> (raw)
In-Reply-To: <5306FA43.1070408@codesourcery.com>
On 02/21/2014 07:03 AM, Yao Qi wrote:
> On 02/21/2014 02:11 PM, asmwarrior wrote:
>> Windows: Fix target_xfer_partial: Assertion `*xfered_len > 0' failed.
>> The failure was introduced in commit 9b409511d07fe375284701af34909fb539029caf, 2014-02-11.
>> gdb/windows-nat.c (windows_xfer_shared_libraries) : If len is 0, it should return TARGET_XFER_EOF.
>
> The format of the changelog entry isn't correct. On the other hand,
> changelog entry is about "what are changed", so "it should return
> TARGET_XFER_EOF" doesn't describe "what are changed" clearly. I suggest
> something below. Otherwise, I don't have comments.
Thanks You. This is definitely OK. Could you put it in?
- return TARGET_XFER_OK;
+ return len ? TARGET_XFER_OK : TARGET_XFER_EOF;
(Please write 'len != 0' though.)
>
> 2014-02-21 Yuanhui Zhang <asmwarrior@gmail.com>
>
> * windows-nat.c (windows_xfer_shared_libraries): Return
> TARGET_XFER_EOF if LEN is zero.
>
--
Pedro Alves
prev parent reply other threads:[~2014-02-21 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 14:35 asmwarrior
2014-02-21 1:22 ` Yao Qi
2014-02-21 6:12 ` asmwarrior
2014-02-21 7:05 ` Yao Qi
2014-02-21 7:37 ` Eli Zaretskii
2014-02-21 7:59 ` Yao Qi
2014-02-21 8:07 ` Eli Zaretskii
2014-02-24 6:47 ` Yao Qi
2014-02-24 7:10 ` asmwarrior
2014-02-24 7:50 ` Yao Qi
2014-02-21 10:13 ` 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=530726DB.2000905@redhat.com \
--to=palves@redhat.com \
--cc=asmwarrior@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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