From: Jan Vrany <jan.vrany@fit.cvut.cz>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
Palmer Dabbelt <palmer@sifive.com>,
Boris Shingarov <boris@shingarov.com>
Subject: Commit 90af06793e breaks RISC-V native target
Date: Tue, 08 Jan 2019 10:26:00 -0000 [thread overview]
Message-ID: <2cda8aec3f030f6cbf5f2176621b01d8194d1521.camel@fit.cvut.cz> (raw)
Hi,
I realized that commit
0af06793e gdb/riscv: Improve logic for when h/w float abi should be used
broke GDB on RISC-V using native target (at least for me):
#include <stdio.h>
int main() {
printf("Test\n");
return 0;
}
./gdb ~/tmp/test
Reading symbols from /home/jv/tmp/test...
(gdb) b main
Breakpoint 1 at 0x5fe: file test.c, line 4.
(gdb) r
Starting program: /home/jv/tmp/test
[1]+ Stopped ./gdb/gdb ~/tmp/test
bfd requires flen 8, but target has flen 0
(gdb)
This is in Debian RISC-V using 4.15 kernel (commit c9dc587367 from [1] which
is essentially SiFive's 4.15 kernel used on Unleashed plus few patches apparently
needed to make GDB native target working).
I've got the same error when running under QEMU and on SiFive's Unleashed board.
Previous commit - 13f2ed32e1 - works fine for me.
I assume things are working for RISC-V guys, so likely I'm missing some bits.
Do I need to apply more kernel patches (if so, which ones?) Anything else to
patch or update in order to make native RISC-V target working again with recent
GDB?
Best, Jan
[1] https://github.com/janvrany/riscv-linux/tree/users/jv/riscv-linux-4.15
next reply other threads:[~2019-01-08 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 10:26 Jan Vrany [this message]
2019-01-08 11:04 ` Andreas Schwab
2019-01-08 21:03 ` Jan Vrany
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=2cda8aec3f030f6cbf5f2176621b01d8194d1521.camel@fit.cvut.cz \
--to=jan.vrany@fit.cvut.cz \
--cc=andrew.burgess@embecosm.com \
--cc=boris@shingarov.com \
--cc=gdb@sourceware.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