Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: Add xmlRegisters= to qsupported query
Date: Mon, 29 Mar 2010 14:13:00 -0000	[thread overview]
Message-ID: <6dc9ffc81003290713p1529c074ia65ff23d5e9a50be@mail.gmail.com> (raw)
In-Reply-To: <834ojz3a4d.fsf@gnu.org>

On Sun, Mar 28, 2010 at 11:38 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> 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.

I will fix it.

>> +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"?

I will add `a'.

> Doesn't it always send the XML description?

Before XML was enabled on x86, we sent

"@<target>\
<architecture>i386</architecture>\
<osabi>GNU/Linux</osabi>\
</target>"

It isn't the "real" XML target description since it doesn't describe anything.

>> @@ -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

Did you mean remote.o wasn't linked in? Can that happen?

> if GDB was built without libexpat?
>

I will add check for HAVE_LIBEXPAT.

Thanks.


-- 
H.J.


  reply	other threads:[~2010-03-29 14:13 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
2010-03-29 14:13       ` H.J. Lu [this message]
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=6dc9ffc81003290713p1529c074ia65ff23d5e9a50be@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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