From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: William Tambe <tambewilliam@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: warning: Target-supplied registers are not supported by the current architecture
Date: Mon, 9 Oct 2023 06:45:45 +0000 [thread overview]
Message-ID: <IA0PR11MB7307FC7C0E62F8927CABF5FCC4CEA@IA0PR11MB7307.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAF8i9mM7S8_nCa1k0EEBNKTDQHz=KLYZ3RA3tQ1R8Ej6W7uhsw@mail.gmail.com>
On Monday, October 9, 2023 1:14 AM, William Tambe wrote:
> I am working on gdbserver support.
>
> I am able to remotely execute the executable and set breakpoints,
> however right after issuing the `target remote` command, I am getting
> following warning:
>
> (gdb) target remote 192.168.1.164:2000
> Remote debugging using 192.168.1.164:2000
> warning: Target-supplied registers are not supported by the current architecture
>
> Error message is coming from gdb/target-descriptions.c at line 576,
> due to data->arch_regs.empty () return true.
>
> Any idea what I might have missed causing data->arch_regs.empty () to
> return true ?
When gdbserver is started with the --remote-debug flag, it prints the
received and sent RSP packages. There, the target description XML would
be seen. I'd suggest starting with inspecting if the contents of that XML
look right.
Regards
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2023-10-09 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 23:13 William Tambe
2023-10-09 6:45 ` Aktemur, Tankut Baris [this message]
2023-10-09 10:46 ` William Tambe
2023-10-09 11:23 ` Luis Machado
2023-10-09 12:09 ` William Tambe
2023-10-09 12:18 ` Luis Machado
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=IA0PR11MB7307FC7C0E62F8927CABF5FCC4CEA@IA0PR11MB7307.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.com \
--cc=gdb@sourceware.org \
--cc=tambewilliam@gmail.com \
/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).