The VTune™ Amplifier XE may display a warning about “Symbol file not found” during Hotspots, Concurrency, or Locks and Waits analysis. For example:
>/opt/intel/vtune_amplifier_xe_2011/bin64/amplxe-cl -collect hotspots -r test1 – my_test_exe
Warning: Symbol file is not found.
The call stack passing through the module [vdso] may be incorrect Using result path `/home/vtsymbal/test1 Executing actions 75 % Generating a report Summary --
----- Elapsed Time: 6.354 CPU Time: 6.210
Executing actions 100 % done
The tool notifies that there is a module [vdso] that cannot be resolved for symbols (the brackets are used for that purpose) and therefore the call stack may be incorrect. In some cases it might be a [vsyscall] module. You may check that the vdso module is in a dynamic dependency list:
>ldd -d my_test_exe linux-vdso.so.1
You can safely ignore this warning if you see a reference to the [vdso]. It means that the kernel dynamically made some temporary memory allocations by loading some executable code into memory space. The fact that VTune Amplifier XE throws this warning indicates that some Hotspot samples were taken when that code was running. During post-processing time VTune Amplifier XE’s collector could not find the vdso anymore. The module linux-vdso.so.1 (linux-vsyscall.so.1 or linux-gate.so.1 on earlier Linux kernels) is a Virtual Dynamic Shared Object (VDSO), which resides in the address space of the program. This is a virtual library which contains a complex logic that provides user applications with fast access to system functions depending on CPU microarchitecture – either through interrupt mechanism or though the fast system calls smechanism (most applicable for modern CPUs) .