Output Redesign in SystemTap Runtime

Frank Ch. Eigler fche@redhat.com
Tue Apr 26 11:14:00 GMT 2005


Hi -

> [...]
> 	stack (1,0);
> [...]
> generates C code like:
> [...]
> 	_stp_print ("Hi. backtrace is");
> 	_stp_stack (1,0);
> [...]
> <entry uptime_read_proc [1114489190.178160] />
> <text>Hi. backtrace is</text>
> <stack verbose=1> 0xffffffff801bdb01 0xffffffff801bba8a
> 0xffffffff80180e72 0xffffffff80181183 0xffffffff8010e51a </stack>
> [...]

OK, though this focuses too much on the act of printing such data.
More generally, backtrace data can instead be saved in ordinary
systemtap variables, meaning in strings or numbers, and only
eventually printed.  By that time, the exact origins ("this came from
a stack") would be lost, in the absence of heroic measures.

- FChE



More information about the Systemtap mailing list