|
From: Harry M. <hj...@ta...> - 2005-08-09 21:51:02
|
I noticed that there is a callgrind branch in the V3 tree. Is it ready to be used yet? When compiling I had some problems which I'm not sure to pursue b/c it wasn't clear whether there was a point yet. There's no callgrind tool in the current v3 distro, so maybe I'm jumping the gun...? hjm |
|
From: Tom H. <to...@co...> - 2005-08-09 21:57:53
|
In message <ddb8ag$f9q$1...@se...>
Harry Mangalam <hj...@ta...> wrote:
> I noticed that there is a callgrind branch in the V3 tree. Is it ready to
> be used yet? When compiling I had some problems which I'm not sure to
> pursue b/c it wasn't clear whether there was a point yet.
Which tree are you talking about? There's no callgrind branch in
the valgrind.org repository as far as I know.
> There's no callgrind tool in the current v3 distro, so maybe I'm jumping
> the gun...?
As callgrind is not part of the main valgrind distribution and never
has been this is not surprising.
I believe Josef is working on a valgrind 3 compatible version of
callgrind which I'm sure will be available in due course from the
usual place.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Harry M. <hj...@ta...> - 2005-08-11 01:51:52
|
Tom Hughes wrote: > In message <ddb8ag$f9q$1...@se...> > Harry Mangalam <hj...@ta...> wrote: > >> I noticed that there is a callgrind branch in the V3 tree. Is it ready >> to >> be used yet? When compiling I had some problems which I'm not sure to >> pursue b/c it wasn't clear whether there was a point yet. > > Which tree are you talking about? There's no callgrind branch in > the valgrind.org repository as far as I know. Argh! Mistake on my part. Foolish transposition of text made me think I had got a callgrind tree - instead I had just checked valgrind into a dir NAMED callgrind. Stupid, stupid. Sorry! hjm -- Cheers, Harry Harry J Mangalam hj...@ta... <<plain text preferred>> |