- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I am trying to profile my application with VTune 2022.
I do it with attach option for both GUI and CLI.
I have instrumented my code and successfully built it.
My code consists of several libs both dynamic and static and I link necessary VTune libs to every my lib in interest.
Every time when I get analysis reports it is missing instrumentation data.
What could be possible reasons for such missing?
Thanks
Link Copied
- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Alexander,
Since your issue is resolved, can we close this issue?
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It start to work in reproducer but I want to make it working in real code.
Right now I get the next error
Of course I have ensured these env variables are set and visible from my application and app is linked with dl and pthread libs:
swuser@x1-ab6:~/alexv/cmp/xswitch$ ldd ./build/X1/bin/xsw-test-server
linux-vdso.so.1 (0x00007fff639b3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f9e123fc000)
libthrift-0.9.2.so => /usr/local/lib/libthrift-0.9.2.so (0x00007f9e1214b000)
libjsoncpp.so.1 => /usr/lib/x86_64-linux-gnu/libjsoncpp.so.1 (0x00007f9e11f19000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f9e11d15000)
libmnl.so.0 => /lib/x86_64-linux-gnu/libmnl.so.0 (0x00007f9e11b0f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9e11771000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9e11380000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9e14b4c000)
libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f9e11118000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f9e10cd4000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f9e1094b000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f9e10733000)
Alexander
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Alexander,
I have been unable to reproduce this issue.
From your screenshot, it appears you are running the VTune Profiler GUI on a Windows system with the a long path to the project directory, and attaching to a process on a remote Linux system.
Can you consistently reproduce this problem?
If so, please exit and restart the VTune GUI from a command prompt with the following steps (you may have to adjust the path to match your installation):
"\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\vtune-vars.bat"
vtune-gui --project-path="\VTuneData"
and rerun your data collection.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is still the same :
and I still can't see __itt tasks or frames
Thanks,
Alexander
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Alexander,
Are you still seeing this issue? If so, Please attach the full results directory (.zip or .tar).
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Alexander,
If you are still seeing this issue, please attach a .tar or .zip of the full results directory.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Alexander,
If you are still seeing this issue, please attach a .tar or .zip of the full results directory.
If I do not hear from you by the end of the week, I will assume that this is no longer an issue for you and close the case from Intel's perspective (it will remain open in the community forum, but unmonitored from Intel).
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Alexander,
Since I have not received any responses lately, I am closing this case from Intel's perspective. It will remain open in the community forum, but unmonitored from Intel.
Thank you.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »