Output Redesign in SystemTap Runtime

[Frank Ch. Eigler]

Hi -

> > More generally, backtrace data can instead be saved in ordinary
> > systemtap variables [...]
> > By that time, the exact origins ("this came from
> > a stack") would be lost, in the absence of heroic measures.
> 
> Not really.  "<stack> 0xf0001234 ...  </stack>" gets saved as a string
> [...]

OK, that's the sort of "heroic measure" I was talking about.  So now
we have a string that has some self-descriptive content markup.  If
this value is then printed with whatever basic tracing function, do
you anticpate nesting this stuff?  i.e.,

    <text><stack>....blah...</stack></text>

Or do you want to obligate a person to call a stack-only printing
function on such saved strings?  Then why bother with the stored
markup?

This is why I say you need to think about this not just from the point
of view of a stack-printing function, but from the end-to-end view of
data being queried, stored, printed, and perhaps ultimately decoded.

- FChE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/systemtap/attachments/20050426/99b672e6/attachment.sig>