Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/6] core_xfer_shared_libraries and core_xfer_shared_libraries_aix returns ULONGEST
Date: Thu, 06 Feb 2014 14:43:00 -0000	[thread overview]
Message-ID: <52F39F88.5020307@redhat.com> (raw)
In-Reply-To: <1391139325-2758-3-git-send-email-yao@codesourcery.com>

On 01/31/2014 03:35 AM, Yao Qi wrote:
> This patch specifies the return value of core_xfer_shared_libraries_aix
> and core_xfer_shared_libraries, and change return value to ULONGEST.
> 
> The following patch can check its return value in core_xfer_partial
> and return appropriate target_xfer_status in core_xfer_partial.

I got a little confused reading this.  I suggest:

 This patch documents the return value of core_xfer_shared_libraries_aix
 and core_xfer_shared_libraries gdbarch hooks, and changes their return
 type to ULONGEST from LONGEST.

 In a following patch, core_xfer_partial is changed to check their
 return values and return an appropriate target_xfer_status.

>  # Read offset OFFSET of TARGET_OBJECT_LIBRARIES formatted shared libraries list from
> -# core file into buffer READBUF with length LEN.
> -M:LONGEST:core_xfer_shared_libraries:gdb_byte *readbuf, ULONGEST offset, ULONGEST len:readbuf, offset, len
> +# core file into buffer READBUF with length LEN.  Return the number of bytes read (
> +# zero indicates failure).

Nit, please put the opening '(' on the next line.  Looks a little odd to me
that way.   Like:

> +# core file into buffer READBUF with length LEN.  Return the number of bytes read
> +# (zero indicates failure).

Otherwise OK.

Thanks,
-- 
Pedro Alves


  reply	other threads:[~2014-02-06 14:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  3:37 [PATCH 0/6] Return target_xfer_status in to_xfer_partial Yao Qi
2014-01-31  3:37 ` [PATCH 1/6] Tweak in memory_error Yao Qi
2014-02-06 12:41   ` Pedro Alves
2014-02-07  4:21     ` Yao Qi
2014-01-31  3:37 ` [PATCH 2/6] core_xfer_shared_libraries and core_xfer_shared_libraries_aix returns ULONGEST Yao Qi
2014-02-06 14:43   ` Pedro Alves [this message]
2014-02-07  4:21     ` Yao Qi
2014-01-31  3:38 ` [PATCH 6/6] Update comments to to_xfer_partial implementations Yao Qi
2014-01-31  3:50   ` Joel Brobecker
2014-01-31  3:38 ` [PATCH 3/6] Replace -1 with TARGET_XFER_E_IO Yao Qi
2014-02-06 14:43   ` Pedro Alves
2014-01-31  3:38 ` [PATCH 4/6] Return early in target_xfer_partial when LEN is zero Yao Qi
2014-02-06 14:44   ` Pedro Alves
2014-01-31  3:39 ` [PATCH 5/6] Return target_xfer_status in to_xfer_partial Yao Qi
2014-02-06 14:44   ` Pedro Alves
2014-02-07  2:11     ` Yao Qi
2014-02-11  6:35     ` Yao Qi

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=52F39F88.5020307@redhat.com \
    --to=palves@redhat.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