Do you have full debug/symbolinformation for the modules that are affected? Doe this happen for all modules, or are you able to see the functions in some modules but not others? Sometimes the module name is provided if VTune Amplifier XE cannot resolve the function names from the available debug information.
Can you post the command lines that you are using to collect the data and generate the report?
When you build your application, you should have the compiler generatesymbol debuginformation. This can usually be done via a compile flag. For example, the -g flag for gcc. This information contains the source code locations of the instructions in the binary and is required to correlate data to source.
If you have this data inyour source, you mayneed to add theflag to the amplxe-cl -collect commandto tellVTune Amplifier XE where to find the information. For example add this flag:
To specify the top level directory to search recursively for all source, symbol, and binary information.
Have you tried using the tachyon sample in the Getting Started Tutorials? I recommend trying this to see if you can get source code information on a sample that has been tested and verified.
Thanks for the information. Since you are using a shell script there are a few things to try. Was the you mention above one of the executables from the script? If so, then you should have the necessary symbol information from the compiler. The next thing I would try would be adding the -follow-child flag the collection command.
Also, does the script finish before the executables or is it written in such a way that the script waits to finish?