Community
cancel
Showing results for 
Search instead for 
Did you mean: 
dan_p
Beginner
100 Views

Symbolic link for shared object file

Jump to solution
Hi,
I'm running Vtune 9.0 on windows using the Linux remote agent. I'm trying to tune my program, that uses some shared objects (Dlls). I'm configuring the .so file in the "Module of intrest", but one .so file is a symbolic link to another .so file - when doing that the VTune can't find the "real" .so file - the one that the symbolic link pointing at.

What am I doing wrong?? :)

Thanks,
Dan
0 Kudos
1 Solution
Vladimir_T_Intel
Moderator
100 Views
Quoting - dan_p
Hi,
I'm running Vtune 9.0 on windows using the Linux remote agent. I'm trying to tune my program, that uses some shared objects (Dlls). I'm configuring the .so file in the "Module of intrest", but one .so file is a symbolic link to another .so file - when doing that the VTune can't find the "real" .so file - the one that the symbolic link pointing at.

What am I doing wrong?? :)

Thanks,
Dan

Hi Dan,

There is a limitation on using symlinks for MOI in the Callgraph. Callgraph instrumentation engine can't find the absolute path properly for coping the .so file to the cache in this case. Unfortunately, it's not described in the Release Notes. The workaround would be either using hardlinks or setting path to the original .so file as MOI.

View solution in original post

1 Reply
Vladimir_T_Intel
Moderator
101 Views
Quoting - dan_p
Hi,
I'm running Vtune 9.0 on windows using the Linux remote agent. I'm trying to tune my program, that uses some shared objects (Dlls). I'm configuring the .so file in the "Module of intrest", but one .so file is a symbolic link to another .so file - when doing that the VTune can't find the "real" .so file - the one that the symbolic link pointing at.

What am I doing wrong?? :)

Thanks,
Dan

Hi Dan,

There is a limitation on using symlinks for MOI in the Callgraph. Callgraph instrumentation engine can't find the absolute path properly for coping the .so file to the cache in this case. Unfortunately, it's not described in the Release Notes. The workaround would be either using hardlinks or setting path to the original .so file as MOI.

View solution in original post

Reply