From: Jim Wilson <jimw@sifive.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: "Simon Marchi" <simark@simark.ca>,
"Maciej W. Rozycki" <macro@wdc.com>,
jiangshuai_li@c-sky.com, guoren@kernel.org,
gdb-patches@sourceware.org, 夏立方 <lifang_xia@c-sky.com>,
yunhai_shang <yunhai_shang@c-sky.com>
Subject: Re: [PATCH] riscv: add gdbserver support
Date: Wed, 22 Jan 2020 00:45:00 -0000 [thread overview]
Message-ID: <CAFyWVaatjqFstKSSW2OtkaSq76rjpia0hZ6WtaTP3WQm2tRaBw@mail.gmail.com> (raw)
In-Reply-To: <20200121130036.GI3865@embecosm.com>
On Tue, Jan 21, 2020 at 5:00 AM Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
> [1] https://fedoraproject.org/wiki/Architectures/RISC-V/Installing
>
> If anyone knows of some instructions that will result in a RISC-V VM
> that works (defined as can configure/build GDB) do please let me know.
The instructions should work. RISC-V Fedora started a mass rebuild in
mid January, but the images listed by virt-builder should be OK. Also
keep in mind that you could be hitting a qemu bug, and you might want
to try a different qemu version or top of tree for the qemu sources.
There is a known bug in the RISC-V qemu-4.2 port that can causes FP
programs to fail for instance, a patch was contributed last week to
fix this. It helps if you mention exactly which fedora image you are
using and exactly which qemu version you are using.
Jim
next prev parent reply other threads:[~2020-01-22 0:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 5:01 jiangshuai_li
2020-01-20 23:33 ` Jim Wilson
2020-01-21 0:30 ` Maciej W. Rozycki
2020-01-21 2:13 ` Simon Marchi
2020-01-21 2:17 ` Maciej W. Rozycki
2020-01-21 13:01 ` Andrew Burgess
2020-01-21 13:28 ` Andrew Burgess
2020-01-21 13:47 ` Andreas Schwab
2020-01-22 0:11 ` Jim Wilson
2020-01-22 0:45 ` Jim Wilson [this message]
2020-01-22 10:19 ` Jim Wilson
2020-01-22 14:08 ` Andrew Burgess
2020-01-21 23:56 ` Jim Wilson
2020-01-22 5:26 ` Guo Ren
2020-01-22 6:15 ` Jim Wilson
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=CAFyWVaatjqFstKSSW2OtkaSq76rjpia0hZ6WtaTP3WQm2tRaBw@mail.gmail.com \
--to=jimw@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=guoren@kernel.org \
--cc=jiangshuai_li@c-sky.com \
--cc=lifang_xia@c-sky.com \
--cc=macro@wdc.com \
--cc=simark@simark.ca \
--cc=yunhai_shang@c-sky.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