|
From: Josef W. <Jos...@gm...> - 2004-03-24 12:41:41
|
On Tuesday 23 March 2004 14:54, Avery Pennarun wrote:
> On Tue, Mar 23, 2004 at 01:00:18PM +0100, Josef Weidendorfer wrote:
> > So the conversion would have to calculate inclusive costs from the self
> > cost of contexts.
>
> Sounds easy enough...
>
> > Another thing: doesn't massif provide the difference "Allocated" -
> > "Deallocated"? I'm not quite sure how to handle this.
>
> Well, it actually provides the continuous sum of allocated-deallocated over
> the runtime of the program. But that doesn't matter: the point is it
> provides just one major number per context ("the spacetime"), which we
> ought to be able to view in kcachegrind like the other numbers (cache
> misses, CPU cycles, etc).
You are right. It's only a matter of writing a conversion script from massif
data (raw/ASCII ?) to cachegrind/calltree format.
KCachegrind should be able to cope with multiple cachegrind/calltree simple
concatenated together (for multiple consensi). The format is described in a
HTML documentation in the calltree package.
Any volunteers?
Cheers,
Josef
>
> Have fun,
>
> Avery
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
|