From: "EBo" <ebo@sandien.com>
To: "Daniel Jacobowitz" <drow@false.org>,
"Michael Snyder" <msnyder@vmware.com>
Cc: "Pedro Alves" <pedro@codesourcery.com>,
"Stan Shebs" <stan@codesourcery.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: multi-proc: info processes?
Date: Thu, 13 Nov 2008 08:09:00 -0000 [thread overview]
Message-ID: <twig.1226563699.82099@swcp.com> (raw)
In-Reply-To: <20081113045618.GA12133@caradoc.them.org>
Just in case you guys need to get into parsing XML I would mention Spirit++ (a
C++ functional template library which replaces most of the functionality of
LEX and YACC -- see http://spirit.sourceforge.net/ for more info). IIRC,
Spirit++ has a XML parser library suite. I do not know if this is appropriate
for the problem, but is a nice tool in the shed when needed.
EBo --
Daniel Jacobowitz <drow@false.org> said:
> On Wed, Nov 12, 2008 at 05:47:38PM -0800, Michael Snyder wrote:
> > Hmmm, isn't the formatting of xml a little heavy-weight for a stub?
>
> Nope. *Parsing* XML is a bit heavy-weight, but generating it requires
> only a tiny routine to escape characters if you support arbitrary
> names in the generated XML; you can generate it textually, not
> via a DOM. gdbserver does this, for instance, and I'd guess it's just
> a couple hundred bytes of code. No more than it would take for a
> qfThreadInfo analogue.
>
> --
> Daniel Jacobowitz
> CodeSourcery
next prev parent reply other threads:[~2008-11-13 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 20:04 Michael Snyder
2008-11-12 20:20 ` Stan Shebs
2008-11-12 20:51 ` Vladimir Prus
2008-11-12 21:22 ` Michael Snyder
2008-11-12 21:30 ` Pedro Alves
2008-11-12 23:16 ` Michael Snyder
2008-11-13 1:48 ` Michael Snyder
2008-11-13 4:57 ` Daniel Jacobowitz
2008-11-13 8:09 ` EBo [this message]
2008-11-13 8:21 ` Vladimir Prus
2008-11-13 23:19 ` Michael Snyder
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=twig.1226563699.82099@swcp.com \
--to=ebo@sandien.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.com \
--cc=stan@codesourcery.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