Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Weimin Pan <weimin.pan@oracle.com>
Cc: qiyaoltc@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PING] [PATCH v3] gdb: ADI support
Date: Wed, 12 Jul 2017 00:43:00 -0000	[thread overview]
Message-ID: <4d405b43-8c9f-c6fd-ab83-d0de9f698cb9@redhat.com> (raw)
In-Reply-To: <98885f9a-7c06-4ab5-b9a2-342277839cc4@default>

On 07/12/2017 01:36 AM, Weimin Pan wrote:
> Simply using target_fileio_xxx routines to replace their
> corresponding open/pread64/pwrite64/close calls, as you
> suggested, does solve the cross-referencing problem. 
> The cross gdb build for all targets was then retried and 
> was successful.

Great.  If you can make sure that the new test runs
FAIL free against gdbserver too, that'll be super.

Note that this /proc reading won't work with core debugging,
of course.  If it makes sense to inspect ADI state in core
dumps, and the info is actually available in the cores, the
target_object / target_xfer path may be the way to go.
But that can be left for later if you'd like.

Thanks,
Pedro Alves


  reply	other threads:[~2017-07-12  0:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12  0:36 Weimin Pan
2017-07-12  0:43 ` Pedro Alves [this message]
2017-07-12  3:25   ` Wei-min Pan
  -- strict thread matches above, loose matches on Subject: below --
2017-07-06 18:36 Weimin Pan
2017-07-10 10:38 ` Yao Qi
2017-07-11  2:56   ` Wei-min Pan
2017-07-11  8:21     ` Yao Qi
2017-07-11 12:21     ` Pedro Alves
2017-07-14  2:33   ` Wei-min Pan
2017-07-14 11:40     ` 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=4d405b43-8c9f-c6fd-ab83-d0de9f698cb9@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    --cc=weimin.pan@oracle.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