This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PING] [PATCH v3] gdb: ADI support
- From: Pedro Alves <palves at redhat dot com>
- To: Weimin Pan <weimin dot pan at oracle dot com>
- Cc: qiyaoltc at gmail dot com, gdb-patches at sourceware dot org
- Date: Wed, 12 Jul 2017 01:43:44 +0100
- Subject: Re: [PING] [PATCH v3] gdb: ADI support
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=palves at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 81F3F3DE3D
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 81F3F3DE3D
- References: <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