From: Jim Wilson <jimw@sifive.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, Palmer Dabbelt <palmer@sifive.com>,
John Baldwin <jhb@freebsd.org>
Subject: Re: [RFC] gdb/riscv: Add read_description method for riscv_linux_nat_target
Date: Thu, 29 Nov 2018 02:23:00 -0000 [thread overview]
Message-ID: <CAFyWVabMg7KYrE64GBz2qLcNJob=zOJLjWg0cFz1De-mRFoM+A@mail.gmail.com> (raw)
In-Reply-To: <20181128224953.22441-1-andrew.burgess@embecosm.com>
On Wed, Nov 28, 2018 at 2:49 PM Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
> Adds riscv_linux_nat_target::read_description method to find a
> suitable target description for the native linux target we are running
> on.
I tested this on my HiFive Unleashed running a 4.15 kernel with
patches for gcc, gdb, and glibc support. It looks good. It correctly
detects the FP register support. I get 3 extra failures
FAIL: gdb.base/solib-display.exp: NO: continue
FAIL: gdb.base/solib-display.exp: IN: continue
FAIL: gdb.base/solib-display.exp: SEP: continue
which looks a little odd since there is no obvious connection to the
target description support, but this is repeatable so something is
going on here. Anyways, I'm OK with this for now, we can worry about
debugging this problem later.
Jim
next prev parent reply other threads:[~2018-11-29 2:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 22:50 Andrew Burgess
2018-11-28 23:37 ` Jim Wilson
2018-11-29 2:23 ` Jim Wilson [this message]
2018-11-29 16:50 ` [PATCH 4/4] " Andrew Burgess
2018-11-29 22:22 ` Jim Wilson
2018-11-29 16:50 ` [PATCH 2/4] gdb/riscv: Add equality operators to riscv_gdb_features Andrew Burgess
2018-11-29 16:50 ` [PATCH 3/4] gdb/riscv: Create each unique target description only once Andrew Burgess
2018-11-29 18:12 ` Pedro Alves
2018-11-29 19:17 ` Andrew Burgess
2018-11-29 22:32 ` Andrew Burgess
2018-11-30 17:07 ` Pedro Alves
2018-11-29 16:50 ` [PATCH 1/4] gdb/riscv: Make some target description functions constant Andrew Burgess
2018-11-29 16:50 ` [PATCH 0/4] Re: gdb/riscv: Add read_description method for riscv_linux_nat_target Andrew Burgess
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='CAFyWVabMg7KYrE64GBz2qLcNJob=zOJLjWg0cFz1De-mRFoM+A@mail.gmail.com' \
--to=jimw@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=palmer@sifive.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