I am running an executable under VTune (2017 Update 2 (build 499904)). When I run the executable outside of Vtune, it exits normally and returns to the prompt in Linux (uname -a output: Linux sklad2.cluster.local 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux). However in vtune it fails to return to prompt or in the GUI it fails to stop profiling. If I force-kill the application being profiled, no data has been recorded. The application continues to run and subsequently consumes more CPU resources than is expected. What is causing this behavior? What should I look at?
Normal execution run
./ITK/build-icc-004-avx2-ipo/bin/ITKLevelSetsv4TestDriver itkMultiLevelSetMalcolmImageSubset2DTest Domain map computed Level set container created LevelSet 0: CV internal term created LevelSet 0: CV external term created Term container 0 created Equation container created Stopping criterion created
ldd ~/ITK/build-icc-004-avx2-ipo/bin/ITKLevelSetsv4TestDriver linux-vdso.so.1 => (0x00007ffdf6b61000) libm.so.6 => /lib64/libm.so.6 (0x00007f2881a6b000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f288184f000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f288164b000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f2881341000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f288112b000) libc.so.6 => /lib64/libc.so.6 (0x00007f2880d6a000) /lib64/ld-linux-x86-64.so.2 (0x00007f2881d8a000)
Command line for running vtune which causes hang
/opt/intel/vtune_amplifier_xe_2017.2.0.499904/bin64/amplxe-cl -collect hotspots -knob enable-user-tasks=false -r /tmp/r005hs --duration 70 -- $HOME/ITK/build-icc-004-avx2-ipo/bin/ITKLevelSetsv4TestDriver itkMultiLevelSetMalcolmImageSubset2DTest
Could you please provide VTune output? Was the hang during application run under profiling or during result finalization phase when the app finished its work?
Thanks & Regards, Dmitry
There is no output to report. VTune simply hangs upon running the profiling of the application. The application continues running, abnormally. It can only be killed with terminal signals such as 9 or 14. This is abnormal behavior for the application and for Vtune.