From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: Using XML in GDB?
Date: Thu, 26 Jan 2006 22:02:00 -0000 [thread overview]
Message-ID: <20060126215731.GB17685@nevyn.them.org> (raw)
In-Reply-To: <200601262140.k0QLesNa008856@elgar.sibelius.xs4all.nl>
On Thu, Jan 26, 2006 at 10:40:54PM +0100, Mark Kettenis wrote:
> No software patents here yet ;-). And some laws that explicitly allow
> for interoperability.
You're a lucky man in a smart country.
In any case, to change the subject. To people whose targets don't
already come with SPIRIT, I don't think there's any benefit in using
it; while it can accomodate GDB's current needs, it's a ridiculous
amount of overkill. Like swatting a fly with a well-targeted asteroid.
To people whose targets _do_ come with SPIRIT descriptions, i.e. mostly
SoC designers, I suspect that GDB support for those descriptions could
be incredibly handy. But we're never going to pull this kind of data
over the wire, so I think it represents a more or less orthoganal
feature to my current plans. I'm not going to pursue it.
If it builds automatically in a GDB source tree, do you have any
concerns about using a third-party XML parser?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-26 21:57 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
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 [this message]
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=20060126215731.GB17685@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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