When you run "vtl", it checks for space on the global data directory. The way it does this is with a shell script and parsing the output of a "df -k".
My Altix has a df -k that looks like this....
pkerney@pkaltix: 58 % df -k /opt/intel/vtune/global_data
Filesystem 1K-blocks Used Available Use% Mounted on
9568000 7601920 1966080 80% /
pkerney@pkaltix: 59 %
The /dev entry makes it go over a line which breaks the parsing.
Edit file file /opt/intel/vtune/bin/clscripts.common and in the routine "check_minimum_space" add another "getline" to make 3, and change the $2 to $1 just below it.
You should now be operational !!!!!
Now a cheat sheet for running it just to help your learning curve.
Compile your program with an added "-g". Note the "-g" does not disable optimisations, it simply adds symbol information to the executable. ie. "-O3 -g" is a valid set of flags. You are VTuning an optimised binary !!!
Run the app just to make sure it works. (My app was pom3d)Then :-
vtl activity -c sampling -app pom3d run # sampling finds the hotspots
vtl show # find out the results to use
vtl view a1::r1 -processes > aaa.txt # output to a file to make it easier to read
vtl view a1::r1 -modules > aaa.txt
vtl view a1::r1 -hf -mn pom3d > aaa.txt
vtl view a1::r1 -code -fn MAIN__ -mn pom3d > aaa.txt
vtl view a1::r1 -gui # use the little icons in the top left to switch views
vtl activity -c callgraph -app pom3d -moi pom3d run # callgraph show the function paths
vtl view a2::r1 -gui
Message Edited by pkerney on 11-25-2004 08:11 PM< /P>
Message Edited by pkerney on 11-25-2004 08:22 PM