This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: XML(-ish) output?
- From: Albretch Mueller <lbrtchx at gmail dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: systemtap at sourceware dot org
- Date: Thu, 4 Oct 2012 14:16:03 +0000
- Subject: Re: XML(-ish) output?
- References: <CAFakBwjcZ=R--b3T4WNoh62Rv4zTco7-7t-c1eY+DFutv4XLGg@mail.gmail.com> <y0m1uhicljt.fsf@fche.csb>
On 10/1/12, Frank Ch. Eigler <fche@redhat.com> wrote:
>> I couldn't find any reference to generating output files as XML
>> documents in sourceware's documentation per se [...]
>
> One can do so from first principles:
>
> probe FOO {
> printf("<tag attrib=\"foo\">\n");
> printf("<bar/>\n");
> printf("</tag>\n");
> }
>
> How much deeper support for xml generation were you hoping for?
~
Well, as deep as necessary. Why should depth matter? Shouldn't
generating an XML-ish stack be straight forward?
~
> Quoting of some sort?
~
Anything that would let me test its output by generating an XML dump
and then somehow reconstruct original dump based on the XML feed, so
things is idempotent
~
My intention isn't really hacking into binaries, but somehow getting
and tracking -detailed- dependency relationships in binaries and how
they relate to source code. Maybe you know of a better tools or you
have a better idea about how should one approach such a task
~
Any suggestions?
~
thanks
lbrtchx