Re: [Valgrind-users] Error using cachegrind

[Josef W. <Jos...@gm...>]

On Wednesday 16 April 2003 08:31, Biswapesh Chattopadhyay wrote:
> Hi
>
> 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% /
>
> Can someone give me a clue ?

Does your program change its cwd (current working directory) while running?
I thought that on dump time, cachegrind will check for existence of an empty 
cachegrind.out it generates at startup. If it doesn't find it because of a 
change of the cwd, you will see the error, as the dump is always created in 
the cwd.

To work around this, I made the "--base=" option to specify a prefix for dump 
files. Use an absolute path in the prefix. 

Nick, we should add a implementation of getcwd() to V, and use absolute file 
paths. But this still doesn't work with chroot() programs :-(
Another option: --dumpfile-fd=... 

Josef

>
> Thanks in adavnce.