From: William Tambe <tambewilliam@gmail.com>
To: Luis Machado <luis.machado@arm.com>
Cc: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.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 07:09:53 -0500 [thread overview]
Message-ID: <CAF8i9mPdEvRHXjzTY5huV5F547t5GV3a+7w6x+NOnS0N_J8xvQ@mail.gmail.com> (raw)
In-Reply-To: <cbb5f9ab-9c52-477e-925d-f3041c4ee151@arm.com>
On Mon, Oct 9, 2023 at 6:23 AM Luis Machado <luis.machado@arm.com> wrote:
>
> On 10/9/23 11:46, William Tambe via Gdb wrote:
> > On Mon, Oct 9, 2023 at 1:45 AM Aktemur, Tankut Baris
> > <tankut.baris.aktemur@intel.com> wrote:
> >>
> >> 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.
> >
> > Below snippet of the prints when using --remote-debug shows the target
> > description XML.
> > I see a star in front of <reg name ... /> blocks; any idea whether
> > that could be the issue ?
> > In the source code, I am not using an actual XML file, instead, I am
> > manually building the target description XML through calls to
> > tdesc_create_reg:
> > https://github.com/fontamsoc/binutils-gdb/blob/main/gdbserver/linux-pu32-low.cc#L63
> >
> > [remote] getpkt: getpkt ("qXfer:features:read:target.xml:0,1000");
> > [no ack sent]
> > [remote] putpkt_binary_1: putpkt ("$l<?xml version="1.0"?>
> > <!DOCTYPE target SYSTEM "gdb-target.dtd">
> > <target>
> > <architecture>pu32</architecture>
> > <osabi>GNU/Linux</osabi>
> > <feature name="org.gnu.gdb.pu32.core">
> > * <reg name="r0" bitsize="32" type="uint32" regnum="0"/>
> > * <reg name="r1" bitsize="32" type="uint32" regnum="1"/>
> > * <reg name="r2" bitsize="32" type="uint32" regnum="2"/>
> > * <reg name="r3" bitsize="32" type="uint32" regnum="3"/>
> > * <reg name="r4" bitsize="32" type="uint32" regnum="4"/>
> > * <reg name="r5" bitsize="32" type="uint32" regnum="5"/>
> > * <reg name="r6" bitsize="32" type="uint32" regnum="6"/>
> > * <reg name="r7" bitsize="32" type="uint32" regnum="7"/>
> > * <reg name="r8" bitsize="32" type="uint32" regnum="8"/>
> > * <reg name="r9" bitsize="32" type="uint32" regnum="9"/>
> > * <reg name="r10" bitsize="32" type="uint32" regnum="10"/>
> > * <reg name="r11" bitsize="32" type="uint32" regnum="11"/>
> > * <reg name="r12" bitsize="32" type="uint32" regnum="12"/>
> > * <reg name="r13" bitsize="32" type="uint32" regnum="13"/>
> > * <reg name="r14" bitsize="32" type="uint32" regnum="14"/>
> > * <reg name="r15" bitsize="32" type="uint32" regnum="15"/>
> > * <reg name="pc" bitsize="32" type="uint32" regnum="16"/>
> > </feature>
> > </target>
> > #ae"); [noack mode]
> > [remote] getpkt: getpkt ("qXfer:auxv:read::0,1000"); [no ack sent]
> >
> >
> > Any ideas on what I am doing wrong ?
>
> What architecture is this out of curiosity? Are you enabling a new architecture called pu32?
Correct, I am enabling a new architecture called pu32; more detail at
https://github.com/fontamsoc .
>
next prev parent reply other threads:[~2023-10-09 12:10 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
2023-10-09 10:46 ` William Tambe
2023-10-09 11:23 ` Luis Machado
2023-10-09 12:09 ` William Tambe [this message]
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=CAF8i9mPdEvRHXjzTY5huV5F547t5GV3a+7w6x+NOnS0N_J8xvQ@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.com \
--cc=tankut.baris.aktemur@intel.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).