public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28291] [gdb, riscv] FAIL: gdb.base/all-architectures-7.exp: tests: osabi=GNU/Linux: arch=riscv: endian=auto: disassemble 0x0,+4 Date: Mon, 30 Aug 2021 12:39:31 +0000 [thread overview] Message-ID: <bug-28291-4717-G9B8Xy7MFz@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28291-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28291 --- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> --- Fixed by: ... diff --git a/opcodes/riscv-dis.c b/opcodes/riscv-dis.c index 30b42ef3aec..38925f3e05c 100644 --- a/opcodes/riscv-dis.c +++ b/opcodes/riscv-dis.c @@ -793,7 +793,7 @@ print_insn_riscv (bfd_vma memaddr, struct disassemble_info *info) if (status != 0) { (*info->memory_error_func) (status, memaddr, info); - return 1; + return status; } insn = (insn_t) bfd_getl16 (packet); dump_size = riscv_insn_length (insn); ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-08-30 12:39 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-30 10:47 [Bug gdb/28291] New: " vries at gcc dot gnu.org 2021-08-30 10:48 ` [Bug gdb/28291] " vries at gcc dot gnu.org 2021-08-30 10:49 ` vries at gcc dot gnu.org 2021-08-30 10:49 ` vries at gcc dot gnu.org 2021-08-30 10:54 ` vries at gcc dot gnu.org 2021-08-30 11:20 ` vries at gcc dot gnu.org 2021-08-30 11:29 ` [Bug gdb/28291] [gdb, riscv] " vries at gcc dot gnu.org 2021-08-30 11:57 ` vries at gcc dot gnu.org 2021-08-30 12:39 ` vries at gcc dot gnu.org 2021-08-30 12:39 ` vries at gcc dot gnu.org [this message] 2021-08-30 12:48 ` vries at gcc dot gnu.org 2021-08-30 15:30 ` cvs-commit at gcc dot gnu.org 2021-08-30 15:40 ` nelsonc1225 at sourceware dot org 2021-08-30 20:34 ` vries at gcc dot gnu.org 2021-08-31 0:57 ` nelsonc1225 at sourceware dot org
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=bug-28291-4717-G9B8Xy7MFz@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).