|
From: Harry M. <hj...@ta...> - 2005-05-11 20:25:35
|
Answering my own post -
it's called op2calltree in the converters subdir of kcachegrind
^^^^
a leftover from when callgrind was called calltree.
Sorry for the noise.
hjm
Harry Mangalam wrote: (before looking arefully..)
>
> The KCachegrind docs refer to an app called "op2callgrind" to tranlating
> oprofile information to data compatible with kcachegrind. I've not been
> able to find it via google and it does not appear to be in the oprofile
> source tree, nor the callgrind source tree nor the kcachegrind source
> tree.
> Did I miss something? Does anyone have any further info on it?
>
>
> <quote>
> System wide profiling is only permitted to the root user, as all actions
> on the system can be observed. Therefore, the following has to be done as
> root. First, configure the profiling process, using the GUI oprof_start or
> the command line tool opcontrol. Standard configuration should be timer
> mode (TBS, see introduction). To start the measurement, run opcontrol -s.
> Then run the application you are interested in, and afterwards, do a
> opcontrol -d. This will write out the measurement results into files under
> directory /var/lib/oprofile/samples/. To be able to visualize the data in
> KCachegrind, do in an empty directory:
>
>
> opreport -gdf | op2callgrind
>
> This will produce a lot of files, one for every program which was running
> on the system. Each one can be loaded into KCachegrind on its own.
> </quote>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
|