From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: Using XML in GDB?
Date: Fri, 27 Jan 2006 18:57:00 -0000 [thread overview]
Message-ID: <u64o5edeh.fsf@gnu.org> (raw)
In-Reply-To: <20060127180429.GA15726@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 27 Jan 2006 13:04:29 -0500)
> Date: Fri, 27 Jan 2006 13:04:29 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> The proposal I sketched out in May is indeed simple. The bits with
> "architecture-specific data" and "registers tags" are the only hints
> that it may need to evolve in the future. However, there's a lot of
> other things which GDB would like to know about targets, in an ideal
> world. A great example that GDB wouldn't make use of today, but
> could, is Andrew Stubbs' mention of memory maps paired with the recent
> report of backtrace blowing up on uclinux. If we can receive the
> memory map from the remote stub, we can absolutely guarantee that we
> never send reads to outside of RAM when we wanted RAM access.
Can we at least have a pipe-dream list of things we think GDB would
ideally like to know about targets, and how structured each one of
them is?
> If we're going to do that, it would be a real shame not to consider
> localization; most ARM system programmers can probably manage the
> English names of the registers, but if we want to offer help text,
> being able to provide it in Japanese is a big win. So that means
> character encodings, and in turn that means we need to be somewhat
> careful with the contents of descriptions.
That part is something I never understood in your reasoning: XML does
not do anything special to allow UTF-8, nor help you deal with the
resulting non-ASCII text on the GDB side. If the underlying libc
supports UTF-8, you have that now; if it doesn't, you won't be better
off even if the target speaks XML.
> The biggest win of XML, for me, is that there are standard answers to
> all of these problems and standard tools for editing and
> checking XML files.
Is XML the only widely used standard that supports what we want?
next prev parent reply other threads:[~2006-01-27 18:25 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
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 [this message]
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=u64o5edeh.fsf@gnu.org \
--to=eliz@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).