Re: [Valgrind-users] Error using cachegrind

[Biswapesh C. <bis...@tc...>]

I just did:

calltree ./SciTE ~/GNOME2.2/src/anjuta/src/aneditor.cxx

It just creates some 0 byte cachegrind.out.* files :-( No warnings about
unable to write this time though.

Any clues ?

On Wed, 2003-04-16 at 13:38, Nicholas Nethercote wrote:
> On 16 Apr 2003, Biswapesh Chattopadhyay wrote:
> 
> > I'm getting the following error with CVS valgrind + cachegrind skin (
> > alias cachegrind='valgrind --skin=cachegrind --num-callers=25
> > --logfile-fd=6'
> >         /opt/gnome2.2/bin/valgrind
> >
> > ------------------------------------
> > ==6863== error: can't open cache simulation output file
> > `cachegrind.out.6863'
> > ==6863==        ... so simulation results will be missing.
> > ------------------------------------
> >
> > A 0 byte file cachegrind.out.6863 is created. There is sufficient space
> > in the harddisk :
> >
> > Filesystem           1K-blocks      Used Available Use% Mounted on
> > /dev/hda2             37334192  15213876  20223844  43% /
> 
> Is file descriptor 6 legitimate?  Does it work if you let Valgrind's
> output go to stderr as usual?
> 
> N
-- 
Biswa.