From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Using XML in GDB?
Date: Thu, 26 Jan 2006 13:41:00 -0000 [thread overview]
Message-ID: <20060126134124.GA3107@nevyn.them.org> (raw)
In-Reply-To: <43D8BB89.4090900@st.com>
On Thu, Jan 26, 2006 at 12:07:37PM +0000, Andrew STUBBS wrote:
> I don't have anything to add to the XML debate yet. The idea of the
> "target available feature" interface sounds interesting and may be of
> use to us here, but I am having a little difficulty tracking down
> details. I have found the beginning of this conversation in the May
> archives, but it is always harder to find the definitive conclusion.
>
> Is there anywhere you can point me to find the final specification of
> what this interface will include - what features will it describe, what
> aspects of those features are covered? Is it just limited to registers?
There isn't a definitive conclusion because it's evolved substantially
once I began (re-) implementing it. This is what I had two weeks ago:
http://sourceware.org/ml/gdb/2005-05/msg00171.html
But it doesn't look entirely like that any more.
Registers can be generically described without hard-coded GDB
knowledge. Most other features can't, except for their presence or
absence. But the point of suggesting XML is to keep this extensible
should someone have a bright idea :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-26 13:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 7:01 Daniel Jacobowitz
2006-01-26 12:45 ` Andrew STUBBS
2006-01-26 13:41 ` Daniel Jacobowitz [this message]
2006-01-26 16:24 ` Andrew STUBBS
2006-01-26 16:41 ` Daniel Jacobowitz
2006-01-26 17:34 ` Paul Koning
2006-01-26 17:44 ` Andrew STUBBS
2006-01-26 18:55 ` Daniel Jacobowitz
2006-01-26 21:05 ` Mark Kettenis
2006-01-26 21:26 ` Daniel Jacobowitz
2006-01-26 21:57 ` Mark Kettenis
2006-01-26 22:02 ` Daniel Jacobowitz
2006-01-26 22:32 ` Bob Rossi
2006-01-26 20:39 ` Mark Kettenis
2006-01-26 20:43 ` Bob Rossi
2006-01-26 21:41 ` Mark Kettenis
2006-01-26 20:52 ` Daniel Jacobowitz
2006-01-26 21:12 ` Bob Rossi
2006-01-27 0:47 ` Bob Rossi
2006-01-27 18:04 ` Eli Zaretskii
2006-01-27 18:41 ` Daniel Jacobowitz
2006-01-27 18:57 ` Eli Zaretskii
2006-01-27 19:06 ` Paul Koning
2006-01-28 6:33 ` Daniel Jacobowitz
2006-01-28 13:54 ` Jim Blandy
2006-01-29 4:09 ` Eli Zaretskii
2006-01-29 4:27 ` Paul Koning
2006-01-28 5:24 ` Daniel Jacobowitz
2006-01-29 4:33 Paul Schlie
2006-01-29 6:18 ` Jim Blandy
2006-01-29 23:21 ` Daniel Jacobowitz
2006-01-29 23:24 ` Paul Schlie
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=20060126134124.GA3107@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@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