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 tdep/26363] New: internal-error: Got request for bad register number 41
Date: Mon, 10 Aug 2020 14:22:58 +0000 [thread overview]
Message-ID: <bug-26363-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26363
Bug ID: 26363
Summary: internal-error: Got request for bad register number 41
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On openSUSE tumbleweed:
...
(gdb) info all-registers^M
...
foseg 0x0 0^M
fooff 0x0 0^M
fop 0x0 0^M
mxcsr 0x1f80 [ IM DM ZM OM UM PM ]^M
../../gdb/i386-linux-nat.c:530: internal-error: Got request for bad register
number 41.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
FAIL: gdb.xml/tdesc-reload.exp: Run info registers (GDB internal error)
...
In i386-tdep.h we find:
...
enum i386_regnum
{
...
I386_MXCSR_REGNUM = 40, /* %mxcsr */
I386_YMM0H_REGNUM, /* %ymm0h */
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-08-10 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 14:22 vries at gcc dot gnu.org [this message]
2020-08-10 14:25 ` [Bug tdep/26363] [i586] " vries at gcc dot gnu.org
2020-08-10 14:26 ` [Bug tdep/26363] [i586] gdb/i386-linux-nat.c:530: " vries at gcc dot gnu.org
2020-08-12 11:41 ` vries at gcc dot gnu.org
2020-08-12 11:46 ` vries at gcc dot gnu.org
2020-08-12 11:48 ` vries at gcc dot gnu.org
2020-08-12 12:02 ` vries at gcc dot gnu.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-26363-4717@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).