From: Eli Zaretskii <eliz@gnu.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: Add xmlRegisters= to qsupported query
Date: Mon, 29 Mar 2010 06:40:00 -0000 [thread overview]
Message-ID: <834ojz3a4d.fsf@gnu.org> (raw)
In-Reply-To: <20100328234643.GA25607@intel.com>
> Date: Sun, 28 Mar 2010 16:46:43 -0700
> From: "H.J. Lu" <hongjiu.lu@intel.com>
>
> 2010-03-28 H.J. Lu <hongjiu.lu@intel.com>
>
> * gdb.texinfo (General Query Packets): Add xmlRegisters.
I have a few comments to the documentation part:
> +@item xmlRegisters
> +This feature indicates that @value{GDBN} supports supports the XML
^^^^^^^^^^^^^^^^^
two "supports" in a row.
> +target description. If the stub sees @samp{xmlRegisters=} with
> +target specfic strings separated by comma, it can send @value{GDBN}
^^^^^^^^
"by a comma". Also, what do you mean by "it can send", why "can"?
Doesn't it always send the XML description?
> @@ -5943,6 +5944,9 @@ i386_gdbarch_init (struct gdbarch_info info, struct gdbarch_list *arches)
> set_gdbarch_fast_tracepoint_valid_at (gdbarch,
> i386_fast_tracepoint_valid_at);
>
> + /* Tell remote stub that we support XML target description. */
> + register_remote_support_xml ("x86");
A possibly dumb question: what effect will this change in i386-tdep.c
have on i386 targets that don't support remote debugging? How about
if GDB was built without libexpat?
next prev parent reply other threads:[~2010-03-29 6:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 20:48 H.J. Lu
2010-03-28 20:52 ` H.J. Lu
2010-03-28 21:27 ` Pedro Alves
2010-03-28 22:56 ` H.J. Lu
2010-03-28 23:48 ` H.J. Lu
2010-03-28 23:46 ` H.J. Lu
2010-03-29 6:40 ` Eli Zaretskii [this message]
2010-03-29 14:13 ` H.J. Lu
2010-03-29 14:32 ` Eli Zaretskii
2010-03-29 14:47 ` H.J. Lu
2010-03-29 14:55 ` H.J. Lu
2010-03-29 16:19 ` H.J. Lu
2010-03-29 17:49 ` Mark Kettenis
2010-03-29 18:02 ` H.J. Lu
2010-03-30 13:55 ` Pedro Alves
2010-03-30 14:58 ` H.J. Lu
2010-03-30 15:09 ` Pedro Alves
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=834ojz3a4d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@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