public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28609] GDB does not recognize the movn mips instruction
Date: Sun, 06 Mar 2022 17:09:03 +0000 [thread overview]
Message-ID: <bug-28609-4717-QYBIgmrw3C@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28609-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28609
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Last reconfirmed| |2022-03-06
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
Can you try git gdb? Maybe it's been fixed there.
gdb gets its knowledge of assembly from libopcodes, which is
more maintained by the binutils developers. So we may just
reassign this.
The executable is fine to attach, might be helpful.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-06 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 3:13 [Bug gdb/28609] New: " andrew.lamarra at gmail dot com
2022-03-05 14:54 ` [Bug gdb/28609] " andrew.lamarra at gmail dot com
2022-03-06 17:09 ` tromey at sourceware dot org [this message]
2022-03-06 19:19 ` andrew.lamarra at gmail dot com
2022-03-06 20:04 ` tromey at sourceware dot org
2022-03-06 20:12 ` andrew.lamarra at gmail dot com
2022-03-06 21:00 ` andrew.lamarra at gmail dot com
2022-03-07 14:27 ` andrew.lamarra at gmail dot com
2022-03-07 14:31 ` andrew.lamarra at gmail dot com
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-28609-4717-QYBIgmrw3C@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).