Re: Human readable output for function return tracer

[Frédéric Weisbecker]

2008/11/24 Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>:
> I do something like that in my ctracer tool[1], take a look at one of
> the callgraphs:
>
> http://oops.ghostprotocols.net:81/ostra/dccp/tx/


Oh yes, that's what I would see as an end result. Except that it would be more
easy for me to have the time of execution on the left (I don't need the time
they are called since it's just a cost measure).


> I.e. the leaf functions doesn't use {}

I guess I could avoid it too..


> On ctracer I didn't had this problem as I don't trace all functions,
> just the ones that receive as one of its parameters a pointer to the
> desired struct, and this pointer is present in all the trace buffer
> entries,

How do you do this tracing by only passing a structure?

> so as part of postprocessing it separates the callgraphs per
> object.

I would like to separate the callgraph per thread. I'm not sure how. Perhaps
by only drawing a simple

------8<----- switch to task nr x -----------8<-------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/