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] [i586] gdb/i386-linux-nat.c:530: internal-error: Got request for bad register number 41
Date: Wed, 12 Aug 2020 11:46:53 +0000 [thread overview]
Message-ID: <bug-26363-4717-6ahuhNiyPr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26363-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26363
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> Created attachment 12765 [details]
> gdb.sum, gdb.log, outputs/gdb.xml/tdesc-reload/
>
> Reproduced using:
> - osc build openSUSE_Factory i586
> - osc chroot openSUSE_Factory i586
> - make check RUNTESTFLAGS=gdb.xml/tdesc-reload.exp
>
> Got different bad register number though: 53.
To reproduce on command line:
...
$ gdb \
outputs/gdb.xml/tdesc-reload/tdesc-reload \
-batch \
-ex start \
-iex "set tdesc filename outputs/gdb.xml/tdesc-reload/outfile1.xml" \
-ex "info all-registers"
Temporary breakpoint 1 at 0x1196: file tdesc-reload.c, line 21.
Temporary breakpoint 1, main () at tdesc-reload.c:21
21 return 0;
eax 0x56559000 1448448000
ecx 0x9684472e -1769715922
edx 0xffffd8f4 -9996
ebx 0x0 0
esp 0xffffd8b8 0xffffd8b8
ebp 0xffffd8b8 0xffffd8b8
esi 0xf7fc2e44 -134468028
edi 0xf7fc2e44 -134468028
eip 0x56556196 0x56556196 <main+13>
eflags 0x216 [ PF AF IF ]
cs 0x23 35
ss 0x2b 43
ds 0x2b 43
es 0x2b 43
fs 0x0 0
gs 0x63 99
st0 0 (raw 0x00000000000000000000)
st1 0 (raw 0x00000000000000000000)
st2 0 (raw 0x00000000000000000000)
st3 0 (raw 0x00000000000000000000)
st4 0 (raw 0x00000000000000000000)
st5 0 (raw 0x00000000000000000000)
st6 0 (raw 0x00000000000000000000)
st7 0 (raw 0x00000000000000000000)
fctrl 0x37f 895
fstat 0x0 0
ftag 0xffff 65535
fiseg 0x0 0
fioff 0x0 0
foseg 0x0 0
fooff 0x0 0
fop 0x0 0
mxcsr 0x1f80 [ IM DM ZM OM UM PM ]
../../gdb/i386-linux-nat.c:530: internal-error: Got request for bad register
number 53.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
This is a bug, please report it. For instructions, see:
<http://bugs.opensuse.org/>.
../../gdb/i386-linux-nat.c:530: internal-error: Got request for bad register
number 53.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
Aborted (core dumped)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-12 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 14:22 [Bug tdep/26363] New: " vries at gcc dot gnu.org
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 [this message]
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-6ahuhNiyPr@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).