Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: <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 01:22:00 -0000	[thread overview]
Message-ID: <5306A9BC.4080701@codesourcery.com> (raw)
In-Reply-To: <530612A8.4000903@gmail.com>

On 02/20/2014 10:35 PM, asmwarrior wrote:
> The original code return len(len could be 0), but the new code just return TARGET_XFER_OK.
> If len is 0, it should return TARGET_XFER_EOF(it is 0 in enum target_xfer_status declaration.
> 

Yes, good catch!

> So, a patch below is confirmed to fix the assert issue, an obvious fix, right? 
> 

This fix is obvious to me.  Please wait for one day, if maintainers
have no comments, push it in.

>  gdb/windows-nat.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c
> index a570a1a..b76d94d 100644
> --- a/gdb/windows-nat.c
> +++ b/gdb/windows-nat.c
> @@ -2480,7 +2480,7 @@ windows_xfer_shared_libraries (struct target_ops *ops,
>  
>    obstack_free (&obstack, NULL);
>    *xfered_len = (ULONGEST) len;
> -  return TARGET_XFER_OK;
> +  return len ? TARGET_XFER_OK : TARGET_XFER_EOF;
>  }
>  
>  static enum target_xfer_status

You still need a changelog entry.

-- 
Yao (齐尧)


  reply	other threads:[~2014-02-21  1:22 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 [this message]
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

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=5306A9BC.4080701@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=asmwarrior@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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