Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 14:32:00 -0000	[thread overview]
Message-ID: <83iq8f19nq.fsf@gnu.org> (raw)
In-Reply-To: <6dc9ffc81003290713p1529c074ia65ff23d5e9a50be@mail.gmail.com>

> Date: Mon, 29 Mar 2010 07:13:28 -0700
> From: "H.J. Lu" <hjl.tools@gmail.com>
> Cc: gdb-patches@sourceware.org
> 
> >> +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.

So how about this text instead:

 If the stub sees @samp{xmlRegisters=} with target specific strings
 separated by a comma, it will send either an XML target description
 or an XML stub that states only the architecture and the OSABI.

> >> +  /* 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?

I don't know.  The question is, will register_remote_support_xml be
always available fro an i386 target?

Thanks.


  reply	other threads:[~2010-03-29 14:32 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
2010-03-29 14:32         ` Eli Zaretskii [this message]
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=83iq8f19nq.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