public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "emr-gnu at hev dot psu.edu" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/27257] New: Remote debugging i686 target from an x86_64 system produces "Unknown register zmm16h requested"
Date: Wed, 27 Jan 2021 15:15:43 +0000 [thread overview]
Message-ID: <bug-27257-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27257
Bug ID: 27257
Summary: Remote debugging i686 target from an x86_64 system
produces "Unknown register zmm16h requested"
Product: gdb
Version: 9.2
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: remote
Assignee: unassigned at sourceware dot org
Reporter: emr-gnu at hev dot psu.edu
Target Milestone: ---
Debugging a simple "Hello World" program built using "gcc -m32" on an x86_64
system via gdbserver fails.
/opt/gdb-9.2/bin/gdbserver localhost:45678 ./helloworld
Process ./helloworld created; pid=25964
Listening on port 45678
> Separate terminal:
/opt/gdb-9.2/bin/gdb ./helloworld
(gdb) target remote localhost:45678
Remote debugging using localhost:45678
Remote connection closed
(gdb)
> gdbserver terminal:
Remote debugging from host ::1, port 38036
../../../gdb-9.2/gdb/gdbserver/regcache.c:257: A problem internal to GDBserver
has been detected.
Unknown register zmm16h requested
emr:/tmp$ uname -smo
Linux x86_64 GNU/Linux
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-27 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 15:15 emr-gnu at hev dot psu.edu [this message]
2021-11-30 9:08 ` [Bug remote/27257] " vries at gcc dot gnu.org
2021-11-30 9:08 ` [Bug tdep/27257] " vries at gcc dot gnu.org
2021-11-30 9:12 ` vries at gcc dot gnu.org
2022-12-02 16:55 ` emr-gnu at hev dot psu.edu
2022-12-02 17: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-27257-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).