Hello ,everyone. I recently used the VTune 2018 for Xeon Phi 5110p (KNC) but I found some differences in the new version. 

In analysis target tab, I can not find the Intel Xeon Phi coprocessor (native) or  Intel Xeon Phi coprocessor  (offload) tab, comparing with Vtune2016 , so can I use the only choice that local host to test the Xeon Phi program? 

I try this option, but I noticed that in the result report, the Collection and Platform Info :  the OS is Centos and the hostname is not the mic ,but in Vtune2016 running in offload mode the platform will show that : Intel MIC Platform Software Stack and mic0.local  .

So I want to know the program really running in offload mode or just run on CPU? How to explain the platform info ?

If just running on CPU, what should I do to make it running on MIC in Vtune 2018?

Thank you for everyone to spend time reading my question and I very want to know the truth.

Hi,

I'm working on an SGX project, I'm trying to perf-analyze it using VTune with no much success - I'm not getting perf analysis for the enclave dll.

My system:

1. SGX SDK v1.9.106.43403
2. SGX PSW v1.9.105.42329
3. VTune Amplifier 2018 Update 2 (build 550381)
4. Intel i7-7500U
5. Windows 10 Pro Version 1709 OS Build 16299.334

I've tried: running the app through VTune integration with Visual Studio 2015, Standalone VTune launching the app and standalone VTune attaching to process - none of these show perf analysis for the dll running within the enclave. 

Due to my failure perf analyzing my code, I tried working with one of SGX sample projects (getting-started-with-sgx-sdk-for-windows) - it doesn't work as well, looking at the Top-down Tree view in VTune, the last point in stack I'm seeing is from the sgx_urts.dll (I added a dummy loop in the enclave and indeed the sgx_urts.dll is accountable for most of the app run) - but for some reason it doesn't go beyond that..

Any suggestions how to make it work? known issues that prevent doing so?

Hi, I am desiring to maximize the CPU using VTune similar to how PTUGen used to work to maximize the stress on the system.

Intel, do you have any scripts for VTune which create maximum stress on the CPU which can be run with VTune?

Thanks,
Rob

Hi,

I am new to this forum and intel parallel studio and this may be a very newbie question. I got a university project on a parallel sorting algorithm which i am trying to tune for both MPI performance and threading performance. I have a dual core computer with hyper threading (so 2 physical cores and 4 threads) and i can usually run mpirun -np 4 without any issues to get a quick performance check of my code. When i am trying to run my application with intel parallel studio vtune amplifier like this:

aps .<app name> <parameters>, i get an error like this:

aps Error: [xine:06003] *** Process received signal ***
[xine:06003] Signal: Segmentation fault (11)
[xine:06003] Signal code: Address not mapped (1)
[xine:06003] Failing at address: 0x44000098
[xine:06003] [ 0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fcec42c8390]
[xine:06003] [ 1] /usr/lib/libmpi.so.12(MPI_Comm_rank+0x3e)[0x7fcec474c2de]
[xine:06003] [ 2] /opt/intel/vtune_amplifier_2018.2.0.551022/lib64/libmps.so(stat_init_post+0x6a)[0x7fcec4acf139]
[xine:06003] [ 3] /opt/intel/vtune_amplifier_2018.2.0.551022/lib64/libmps.so(MPI_Init+0xe0)[0x7fcec4a65644]
[xine:06003] [ 4] ./terasort[0x40109b]
[xine:06003] [ 5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fcec3f0d830]
[xine:06003] [ 6] ./terasort[0x401269]
[xine:06003] *** End of error message ***
aps Error: Cannot run the collection.

When i run the app using mpirun, it runs without issues on both my local computer and university HPC cluster. I think i am missing something really basic here. would really appreciate the help. Thanks!

I never thought I would see a BSOD these days but on Windows 7, trying to use ​Intel VTune Amplifier 2018 to profile a simple C++ application causes BSOD ​after which I am left with no option but to reboot the PC. This is a very simple C++ console application, about 10 lines, written just to play around with the VTune product and its capabilities.

​I built the application under 32-bit release mode with Microsoft Visual Studio 2017. Trying to inject __itt_resume() and __itt_pause() calls between the blocks of code I want profiled immediately causes it to BSOD when I start a new Advanced Hotspot Analysis. It also happens *without* the _itt* calls. All I have to do is to start an advanced hotspot analysis (basic hotspot analysis seems to work ok.)

​Any idea what I can do about it? We just paid a hefty sum to purchase this license and I don't want to saddled with an unusable product. Is there any problem with turning on MSVC's /PROFILE option when building the exe? Does that option conflict with VTune?

Hello,

I'm working on a Yocto-based project with Linux kernel 4.14. The hardware platform is Skylake. As far as I understand from documentation VTune Apmplifier requires Media Server Studio installed on target system which also means installing patched 4.4 kernel. Unfortunately, it's not an option. Is it possible to use VTune Amplifier with 4.14? Are there patches or unreleased dev branch for this version? 

Thank you

[Process]
Process Name: amplxe-runss.exe
Virtual Memory Size: 218580K
Working Set Size: 41936K

[Assertion]
CrashedPID: 11644
CrashedTID: 13288
Expression: process != NULL && process->getParentId() == ppid
File: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\event_handler.cpp
Line: 781
Product: Intel(R) VTune(TM) Amplifier 2018 Update 1; 535340
ReportPath: C:\Users\max\AppData\Local\Temp\amplxe-log-max\2018-04-13-12-41-53-752.amplxe-runss.exe\


[Products]
Package ID: N/A
Package Contents: Intel(R) VTune(TM) Amplifier 2018 Update 1
Build Number: 535340


[System]

Host Name:                 DESKTOP-74O9PUR
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.16299 N/A Build 16299
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:   
Product ID:                00330-80000-00000-AA399
Original Install Date:     11/15/2017, 02:40:56 PM
System Boot Time:          4/11/2018, 04:16:25 PM
System Manufacturer:       Hewlett-Packard
System Model:              HP Compaq Elite 8300 CMT
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~3392 Mhz
BIOS Version:              Hewlett-Packard K01 v03.06, 2/12/2018
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC+03:00) Minsk
Total Physical Memory:     16,258 MB
Available Physical Memory: 6,953 MB
Virtual Memory: Max Size:  24,450 MB
Virtual Memory: Available: 11,067 MB
Virtual Memory: In Use:    13,383 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-74O9PUR
Hotfix(s):                 12 Hotfix(s) Installed.
                           [01]: KB4048951
                           [02]: KB4053577
                           [03]: KB4054022
                           [04]: KB4056887
                           [05]: KB4058043
                           [06]: KB4058702
                           [07]: KB4088785
                           [08]: KB4090914
                           [09]: KB4093110
                           [10]: KB4099989
                           [11]: KB4088776
                           [12]: KB4093112
Network Card(s):           2 NIC(s) Installed.
                           [01]: Intel(R) 82579LM Gigabit Network Connection
                                 Connection Name: Ethernet
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.1
                                 IP address(es)
                                 [01]: 192.168.1.165
                                 [02]: fe80::951f:907d:590a:20cc
                                 [03]: 2a00:6440:173:101::f4c
                           [02]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::613f:6697:7dc3:bce4
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes


[ClientInfo]

Report ID: 58c3a1d2-6b39-432a-88a7-3b78a67ef8d7
UUID: {AA1C6D45-4AF2-4D65-B4F8-04F93DB2ED59}


[Dump]
Path: C:\Users\max\AppData\Local\Temp\amplxe-log-max\2018-04-13-12-41-53-752.amplxe-runss.exe\crash.dmp


[PremortalLog]
1458 [13288] WARN perfrun.etw <> - can't find grandparent process for the process with pid 0 and ppid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:430
1544 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1544 [13288] WARN perfrun.etw <> - the thread was not added: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:177
1545 [13288] WARN perfrun.etw <> - can't append the thread: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\event_handler.cpp:711
1545 [13288] WARN perfrun.etw <> - the thread was not added: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:177
1545 [13288] WARN perfrun.etw <> - can't append the thread: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\event_handler.cpp:711
1545 [13288] WARN perfrun.etw <> - the thread was not added: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:177
1545 [13288] WARN perfrun.etw <> - can't append the thread: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\event_handler.cpp:711
1545 [13288] WARN perfrun.etw <> - the thread was not added: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:177
1545 [13288] WARN perfrun.etw <> - can't append the thread: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\event_handler.cpp:711
1545 [13288] WARN perfrun.etw <> - the thread was not added: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:177
1545 [13288] WARN perfrun.etw <> - can't append the thread: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\event_handler.cpp:711
1545 [13288] WARN perfrun.etw <> - the thread was not added: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:177
1545 [13288] WARN perfrun.etw <> - can't append the thread: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\event_handler.cpp:711
1546 [13288] WARN perfrun.etw <> - the thread was not added: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:177
1546 [13288] WARN perfrun.etw <> - can't append the thread: tid = 0; pid = 0, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\event_handler.cpp:711
1546 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 12; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1546 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 16; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1546 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 20; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1546 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 24; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1546 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 28; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1630 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 36; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1630 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 40; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1630 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 44; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1631 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 48; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1631 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 52; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1631 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 56; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1631 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 60; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1631 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 64; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1631 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 68; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1631 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 72; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1632 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 76; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1632 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 80; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1632 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 104; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1632 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 108; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1632 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 112; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1632 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 116; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1632 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 120; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1633 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 124; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1633 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 136; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1633 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 140; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1633 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 144; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1633 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 148; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1633 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 152; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1633 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 156; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1633 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 160; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1634 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 164; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1634 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 168; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1634 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 172; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1634 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 176; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1634 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 180; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1634 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 184; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1634 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 188; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1635 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 200; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1635 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 204; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1635 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 208; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1635 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 212; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1635 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 220; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1635 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 268; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1635 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 272; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1635 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 280; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1636 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 284; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1636 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 288; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1636 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 292; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1636 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 296; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1636 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 300; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1636 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 304; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1636 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 308; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1637 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 312; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1637 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 316; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1637 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 320; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1637 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 324; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1637 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 328; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1637 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 332; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1637 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 336; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1637 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 340; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1638 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 344; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1638 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 348; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1638 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 352; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1638 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 356; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1638 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 396; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1638 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 404; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1638 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 408; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1639 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 412; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1639 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 420; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1639 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 432; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1639 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 436; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1639 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 444; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1639 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 448; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1639 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 464; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1639 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 468; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1640 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 472; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1640 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 476; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1640 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 480; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1640 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 484; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1640 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 488; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1640 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 492; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1640 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 496; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1640 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 500; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166
1641 [13288] WARN perfrun.etw <> - start address isn't inside a known module: tid = 564; pid = 4, at file: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\vcs\perfrun1\plugins\etw\src\kernel\process_tree.cpp:166

[Context.0x000011e8]
EAX: 0x0000000000000000
EBP: 0x000002bed61aa3a8
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff3511ff04
ESI: 0x0000000000000000
ESP: 0x000000faf01ff258
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x000013d8]
EAX: 0x0000000000000000
EBP: 0x000000faef4fd550
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff3511ff04
ESI: 0x0000000000000000
ESP: 0x000000faef4fd478
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x000015d8]
EAX: 0x0000000000000000
EBP: 0x000000faefbfe900
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff3511ff04
ESI: 0x0000000000000000
ESP: 0x000000faefbfe888
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x000017a0]
EAX: 0x0000000000000000
EBP: 0x000000faf02ffb70
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff3511ff04
ESI: 0x0000000000000000
ESP: 0x000000faf02ffa78
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x000029cc]
EAX: 0x0000000000000000
EBP: 0x0000000000000414
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff351209d4
ESI: 0x0000000000000000
ESP: 0x000000faf00ff228
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x000031ec]
EAX: 0x0000000000000000
EBP: 0x000000faefcff630
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff3511ff04
ESI: 0x0000000000000000
ESP: 0x000000faefcfee38
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x000032e4]
EAX: 0x0000000000000000
EBP: 0x000000faf06fe370
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff351205a4
ESI: 0x0000000000000000
ESP: 0x000000faf06fe2b8
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x000033e8]
EAX: 0x00007fff01b0a264
EBP: 0x000000faefdfdc30
EBX: 0x000002bed8f89fb0
ECX: 0x0000000000000000
EDI: 0x000002bed977f840
EDX: 0x00007fff350c1630
EIP: 0x00007fff317b4008
ESI: 0x0000000000000000
ESP: 0x000000faefdfdb30
R10: 0x00007fff01b29800
R11: 0x0000000000000000
R12: 0x000000000000030d
R13: 0x000002bed8f89fb0
R14: 0x000000faefdfddd8
R15: 0x000002bed8f71a90
R8: 0x000000faefdfd608
R9: 0x0000d3601b2d9ff6


[Context.0x00003484]
EAX: 0x0000000000000000
EBP: 0x000000faefaff650
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff351209d4
ESI: 0x0000000000000000
ESP: 0x000000faefaff2d8
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x000036cc]
EAX: 0x0000000000000000
EBP: 0x0000000000000000
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff35123794
ESI: 0x0000000000000000
ESP: 0x000000faef5ff7d8
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x00003798]
EAX: 0x0000000000000000
EBP: 0x0000000000000000
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff35123794
ESI: 0x0000000000000000
ESP: 0x000000faef7ffaf8
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x00003958]
EAX: 0x0000000000000000
EBP: 0x000000faf03ff350
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff3511ffa4
ESI: 0x0000000000000000
ESP: 0x000000faf03ff2b8
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x00004018]
EAX: 0x0000000000000000
EBP: 0x0000000000000000
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff35123794
ESI: 0x0000000000000000
ESP: 0x000000faeffff9c8
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x00004060]
EAX: 0x0000000000000000
EBP: 0x000000faef9ffaa0
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff351209d4
ESI: 0x0000000000000000
ESP: 0x000000faef9ff728
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x00004098]
EAX: 0x0000000000000000
EBP: 0x0000000000000000
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff35123794
ESI: 0x0000000000000000
ESP: 0x000000faefeff858
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x00004304]
EAX: 0x0000000000000000
EBP: 0x0000000000000000
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff35123794
ESI: 0x0000000000000000
ESP: 0x000000faef6ff8d8
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Context.0x0000475c]
EAX: 0x0000000000000000
EBP: 0x000000faef8fef49
EBX: 0x0000000000000000
ECX: 0x0000000000000000
EDI: 0x0000000000000000
EDX: 0x0000000000000000
EIP: 0x00007fff3511ff04
ESI: 0x0000000000000000
ESP: 0x000000faef8fedd8
R10: 0x0000000000000000
R11: 0x0000000000000000
R12: 0x0000000000000000
R13: 0x0000000000000000
R14: 0x0000000000000000
R15: 0x0000000000000000
R8: 0x0000000000000000
R9: 0x0000000000000000


[Module000]
Age: 0x0000000000000001
Base: 0x00007fff35080000
Begin: 0x00007fff35081000
End: 0x00007fff35193000
FullName: C:\WINDOWS\SYSTEM32\ntdll.dll
Guid: 780c0c1b-6159-ae8b-7663-b42759ba7b4e
Size: 0x00000000001e0000
SymbolName: ntdll.pdb
Timestamp: 0x00000000effc9126


[Module001]
Age: 0x0000000000000001
Base: 0x00007fff34ef0000
Begin: 0x00007fff34ef1000
End: 0x00007fff34f63000
FullName: C:\WINDOWS\System32\KERNEL32.DLL
Guid: 1bccd94c-5154-86e0-3396-c7e89525227e
Size: 0x00000000000ae000
SymbolName: kernel32.pdb
Timestamp: 0x000000000c2cf900


[Module002]
Age: 0x0000000000000001
Base: 0x00007fff34e80000
Begin: 0x00007fff34e81000
End: 0x00007fff34ec5000
FullName: C:\WINDOWS\System32\WS2_32.dll
Guid: cf4c0101-147e-bd22-2bac-40066d789722
Size: 0x000000000006c000
SymbolName: ws2_32.pdb
Timestamp: 0x000000009ac9e819


[Module003]
Age: 0x0000000000000001
Base: 0x00007fff34650000
Begin: 0x00007fff34651000
End: 0x00007fff34684000
FullName: C:\WINDOWS\System32\sechost.dll
Guid: 700da429-0140-4e2f-8a39-d001481b8a97
Size: 0x000000000005b000
SymbolName: sechost.pdb
Timestamp: 0x00000000caf94b03


[Module004]
Age: 0x0000000000000001
Base: 0x00007fff32580000
Begin: 0x00007fff32581000
End: 0x00007fff32780000
FullName: C:\WINDOWS\System32\combase.dll
Guid: 7e1b6b31-68d2-00e8-9c33-239fa072f28a
Size: 0x0000000000308000
SymbolName: combase.pdb
Timestamp: 0x000000003db461b4


[Module005]
Age: 0x0000000000000001
Base: 0x00007fff317a0000
Begin: 0x00007fff317a1000
End: 0x00007fff3188e000
FullName: C:\WINDOWS\System32\KERNELBASE.dll
Guid: 141ada76-555f-cf3b-df62-e499523d3170
Size: 0x0000000000266000
SymbolName: kernelbase.pdb
Timestamp: 0x0000000090a96867


[Module006]
Age: 0x0000000000000001
Base: 0x00007fff30c00000
Begin: 0x00007fff30c01000
End: 0x00007fff30c4f000
FullName: C:\WINDOWS\system32\mswsock.dll
Guid: 1afd6eca-ed9e-7dd0-fbd2-f6999a01f7f5
Size: 0x0000000000066000
SymbolName: mswsock.pdb
Timestamp: 0x000000003a7c7ba7


[Module007]
Age: 0x0000000000000001
Base: 0x00007fff1d200000
Begin: 0x00007fff1d201000
End: 0x00007fff1d226000
FullName: C:\Program&nbsp;Files&nbsp;(x86)\IntelSWTools\VTune&nbsp;Amplifier\bin64\amplxe_boost_thread_1.55.dll
Guid: 4dfe7b00-b017-4b33-8331-3a9653a80604
Size: 0x0000000000043000
SymbolName: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\build\build_release_win32-x86_64_icl_15.0.221_mstools_12.0\boost\boost_1.55.0\boost.thread\amplxe_boost_thread_1.55.pdb
Timestamp: 0x000000005a02343d


[Module008]
Age: 0x0000000000000001
Base: 0x00007fff06180000
Begin: 0x00007fff06181000
End: 0x00007fff06232000
FullName: C:\Program&nbsp;Files&nbsp;(x86)\IntelSWTools\VTune&nbsp;Amplifier\bin64\amplxe_qfagentminidump_core_1.18.dll
Guid: 8007942b-82ab-4976-9242-7ce7f631f53d
Size: 0x0000000000131000
SymbolName: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\build\build_release_win32-x86_64_icl_15.0.221_mstools_12.0\qfagentminidump.core\amplxe_qfagentminidump_core_1.18.pdb
Timestamp: 0x000000005a02359c


[Module009]
Age: 0x0000000000000001
Base: 0x00007fff04d60000
Begin: 0x00007fff04d61000
End: 0x00007fff04d93000
FullName: C:\Program&nbsp;Files&nbsp;(x86)\IntelSWTools\VTune&nbsp;Amplifier\bin64\amplxe_qfagent_assert_1.18.dll
Guid: d5178b62-283f-428c-9d5d-3d13b3754442
Size: 0x0000000000064000
SymbolName: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\build\build_release_win32-x86_64_icl_15.0.221_mstools_12.0\qfagentminidump.assert\amplxe_qfagent_assert_1.18.pdb
Timestamp: 0x000000005a02359d


[Module010]
Age: 0x0000000000000001
Base: 0x00007fff04220000
Begin: 0x00007fff04221000
End: 0x00007fff0433c000
FullName: C:\Program&nbsp;Files&nbsp;(x86)\IntelSWTools\VTune&nbsp;Amplifier\bin64\amplxe_cpil_2.18.dll
Guid: 45e55a89-a7dd-4820-961c-e14c30fa0a48
Size: 0x00000000001e9000
SymbolName: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\build\build_release_win32-x86_64_icl_15.0.221_mstools_12.0\cpil\amplxe_cpil_2.18.pdb
Timestamp: 0x000000005a023447


[Module011]
Age: 0x0000000000000001
Base: 0x00007fff03470000
Begin: 0x00007fff03471000
End: 0x00007fff03518000
FullName: C:\Program&nbsp;Files&nbsp;(x86)\IntelSWTools\VTune&nbsp;Amplifier\bin64\MSVCR120.dll
Guid: 3e4edf77-4220-443e-8524-b0a90dfb7699
Size: 0x00000000000ef000
SymbolName: msvcr120.amd64.pdb
Timestamp: 0x00000000524f83ff


[Module012]
Age: 0x0000000000000001
Base: 0x00007ff75d4b0000
Begin: 0x00007ff75d4b1000
End: 0x00007ff75d9f9000
FullName: C:\Program&nbsp;Files&nbsp;(x86)\IntelSWTools\VTune&nbsp;Amplifier\bin64\amplxe-runss.exe
Guid: dcda541e-663d-4755-a0a6-bd6ccf048700
Size: 0x00000000008b5000
SymbolName: C:\bb\INNLphep2w6r\b\b\tmplj_pzx\build\build_release_win32-x86_64_icl_15.0.221_mstools_12.0\perfrun.launcher\amplxe-runss.pdb
Timestamp: 0x000000005a0235a6


[Stack.clean.0x000011e8]
+ | 0x000000faf01ff260 | 0x00007fff3183b62e
+ | 0x000000faf01ff2e0 | 0x00007ff75d9b14b0
+ | 0x000000faf01ffa20 | 0x00007ff75d767e72
+ | 0x000000faf01ffb90 | 0x00007fff1d2050de
+ | 0x000000faf01ffcd0 | 0x00007fff1d204833
+ | 0x000000faf01ffd20 | 0x00007fff34f01fe4
+ | 0x000000faf01ffd50 | 0x00007fff350eefc1


[Stack.clean.0x000013d8]
+ | 0x000000faef4fd480 | 0x00007fff317b3b7f
+ | 0x000000faef4fd520 | 0x00007ff75d5d5f2b
+ | 0x000000faef4fdbd0 | 0x00007ff75d55af3c
+ | 0x000000faef4fe060 | 0x00007ff75d4c2f25
+ | 0x000000faef4fe5c0 | 0x00007ff75d4cae13
+ | 0x000000faef4fe7a0 | 0x00007ff75d4bdf5c
+ | 0x000000faef4ff850 | 0x00007ff75d4b1214
+ | 0x000000faef4ff980 | 0x00007ff75d9f6ebf
+ | 0x000000faef4ff9b0 | 0x00007fff34f01fe4
+ | 0x000000faef4ff9e0 | 0x00007fff350eefc1


[Stack.clean.0x000015d8]
+ | 0x000000faefbfe890 | 0x00007fff30c09137
+ | 0x000000faefbfe930 | 0x00007fff30c11aec
+ | 0x000000faefbfed40 | 0x00007fff34e9727c
+ | 0x000000faefbfedc0 | 0x00007fff34e971a2
+ | 0x000000faefbfee00 | 0x00007ff75d5bfc12
+ | 0x000000faefbff0c0 | 0x00007ff75d5b5998
+ | 0x000000faefbff2f0 | 0x00007ff75d5926d0
+ | 0x000000faefbff780 | 0x00007ff75d5a86d5
+ | 0x000000faefbff7f0 | 0x00007fff1d2050de
+ | 0x000000faefbff930 | 0x00007fff1d204833
+ | 0x000000faefbff980 | 0x00007fff34f01fe4
+ | 0x000000faefbff9b0 | 0x00007fff350eefc1


[Stack.clean.0x000017a0]
+ | 0x000000faf02ffa80 | 0x00007fff317b3b7f
+ | 0x000000faf02ffb20 | 0x00007ff75d5f8bd1
+ | 0x000000faf02ffb50 | 0x00007ff75d5fa47e
+ | 0x000000faf02ffba0 | 0x00007fff03494f7f
+ | 0x000000faf02ffbd0 | 0x00007fff03495126
+ | 0x000000faf02ffc00 | 0x00007fff34f01fe4
+ | 0x000000faf02ffc30 | 0x00007fff350eefc1


[Stack.clean.0x000029cc]
+ | 0x000000faf00ff230 | 0x00007fff317fa9c6
+ | 0x000000faf00ff530 | 0x00007fff3261aa73
+ | 0x000000faf00ff7c0 | 0x00007fff3261ce00
+ | 0x000000faf00ff810 | 0x00007fff3261a931
+ | 0x000000faf00ff870 | 0x00007fff3265157c
+ | 0x000000faf00ff8a0 | 0x00007fff34f01fe4
+ | 0x000000faf00ff8d0 | 0x00007fff350eefc1


[Stack.clean.0x000031ec]
+ | 0x000000faefcfee40 | 0x00007fff3183b62e
+ | 0x000000faefcfeec0 | 0x00007ff75d9b14b0
+ | 0x000000faefcff600 | 0x00007ff75d9b0315
+ | 0x000000faefcfff10 | 0x00007ff75d6ead0b
+ | 0x000000faefcfff60 | 0x00007fff34f01fe4
+ | 0x000000faefcfff90 | 0x00007fff350eefc1


[Stack.clean.0x000032e4]
+ | 0x000000faf06fe2c0 | 0x00007fff3180f109
+ | 0x000000faf06fe330 | 0x00007fff061bbfd6
+ | 0x000000faf06ff740 | 0x00007fff1d2050de
+ | 0x000000faf06ff880 | 0x00007fff1d204833
+ | 0x000000faf06ff8d0 | 0x00007fff34f01fe4
+ | 0x000000faf06ff900 | 0x00007fff350eefc1


[Stack.clean.0x000033e8]
+ | 0x000000faefdfdc10 | 0x00007fff04d61986
+ | 0x000000faefdfdc40 | 0x00007fff04d613a1
+ | 0x000000faefdfdec0 | 0x00007fff042b7799
+ | 0x000000faefdfdef0 | 0x00007ff75d7ecd86
+ | 0x000000faefdfe230 | 0x00007ff75d7f79d3
+ | 0x000000faefdfe5f0 | 0x00007ff75d81d37f
+ | 0x000000faefdfefd0 | 0x00007ff75d81bae9
+ | 0x000000faefdff300 | 0x00007ff75d7c7f97
+ | 0x000000faefdff330 | 0x00007fff34653d81
+ | 0x000000faefdff410 | 0x00007fff34653169
+ | 0x000000faefdff470 | 0x00007fff3465b209
+ | 0x000000faefdff4d0 | 0x00007ff75d7c8dd6
+ | 0x000000faefdff9d0 | 0x00007ff75d7cb625
+ | 0x000000faefdffa00 | 0x00007ff75d7c5405
+ | 0x000000faefdffd50 | 0x00007fff1d2050de
+ | 0x000000faefdffe90 | 0x00007fff1d204833
+ | 0x000000faefdffee0 | 0x00007fff34f01fe4
+ | 0x000000faefdfff10 | 0x00007fff350eefc1


[Stack.clean.0x00003484]
+ | 0x000000faefaff2e0 | 0x00007fff317fa9c6
+ | 0x000000faefaff5e0 | 0x00007fff317fa8ae
+ | 0x000000faefaff620 | 0x00007fff1d208c77
+ | 0x000000faefaff730 | 0x00007ff75d68dc12
+ | 0x000000faefaff7e0 | 0x00007ff75d67ee48
+ | 0x000000faefaff8e0 | 0x00007ff75d67e9b3
+ | 0x000000faefaffa10 | 0x00007ff75d66f3bd
+ | 0x000000faefaffa40 | 0x00007fff1d2050de
+ | 0x000000faefaffb80 | 0x00007fff1d204833
+ | 0x000000faefaffbd0 | 0x00007fff34f01fe4
+ | 0x000000faefaffc00 | 0x00007fff350eefc1


[Stack.clean.0x000036cc]
+ | 0x000000faef5ff7e0 | 0x00007fff350b49dd
+ | 0x000000faef5ffb70 | 0x00007fff34f01fe4
+ | 0x000000faef5ffba0 | 0x00007fff350eefc1


[Stack.clean.0x00003798]
+ | 0x000000faef7ffb00 | 0x00007fff350b49dd
+ | 0x000000faef7ffe90 | 0x00007fff34f01fe4
+ | 0x000000faef7ffec0 | 0x00007fff350eefc1


[Stack.clean.0x00003958]
+ | 0x000000faf03ff2c0 | 0x00007fff317fd3ce
+ | 0x000000faf03ff320 | 0x00007ff75d5fc651
+ | 0x000000faf03ff430 | 0x00007ff75d5f74a1
+ | 0x000000faf03ff620 | 0x00007fff1d2050de
+ | 0x000000faf03ff760 | 0x00007fff1d204833
+ | 0x000000faf03ff7b0 | 0x00007fff34f01fe4
+ | 0x000000faf03ff7e0 | 0x00007fff350eefc1


[Stack.clean.0x00004018]
+ | 0x000000faeffff9d0 | 0x00007fff350b49dd
+ | 0x000000faeffffd60 | 0x00007fff34f01fe4
+ | 0x000000faeffffd90 | 0x00007fff350eefc1


[Stack.clean.0x00004060]
+ | 0x000000faef9ff730 | 0x00007fff317fa9c6
+ | 0x000000faef9ffa30 | 0x00007fff317fa8ae
+ | 0x000000faef9ffa70 | 0x00007fff1d208c77
+ | 0x000000faef9ffb80 | 0x00007fff061d5e12
+ | 0x000000faef9ffc30 | 0x00007fff061ae4ca
+ | 0x000000faef9ffd20 | 0x00007fff1d2050de
+ | 0x000000faef9ffe60 | 0x00007fff1d204833
+ | 0x000000faef9ffeb0 | 0x00007fff34f01fe4
+ | 0x000000faef9ffee0 | 0x00007fff350eefc1


[Stack.clean.0x00004098]
+ | 0x000000faefeff860 | 0x00007fff350b49dd
+ | 0x000000faefeffbf0 | 0x00007fff34f01fe4
+ | 0x000000faefeffc20 | 0x00007fff350eefc1


[Stack.clean.0x00004304]
+ | 0x000000faef6ff8e0 | 0x00007fff350b49dd
+ | 0x000000faef6ffc70 | 0x00007fff34f01fe4
+ | 0x000000faef6ffca0 | 0x00007fff350eefc1


[Stack.clean.0x0000475c]
+ | 0x000000faef8fede0 | 0x00007fff317b3b7f
+ | 0x000000faef8fee80 | 0x00007fff0349b9f8
+ | 0x000000faef8fefb0 | 0x00007fff0349ca24
+ | 0x000000faef8ff000 | 0x00007fff0349c880
+ | 0x000000faef8ff070 | 0x00007fff061b2df3
+ | 0x000000faef8ff200 | 0x00007fff061a270e
+ | 0x000000faef8ff2c0 | 0x00007fff061b8b89
+ | 0x000000faef8ff2f0 | 0x00007fff06216f54
+ | 0x000000faef8ffa20 | 0x00007fff061adf58
+ | 0x000000faef8ffaf0 | 0x00007fff1d2050de
+ | 0x000000faef8ffc30 | 0x00007fff1d204833
+ | 0x000000faef8ffc80 | 0x00007fff34f01fe4
+ | 0x000000faef8ffcb0 | 0x00007fff350eefc1


[CreationLog]
qfagent_1::processAssertionExceptionWindows : 2018-04-13-12-41-56-766 : Assertion report initialized
qfagent_1::processAssertionExceptionWindows : 2018-04-13-12-41-56-771 : Process section is set up in crash report
qfagent_1::runAssertionHandling : 2018-04-13-12-41-56-771 : Started assertion handling in crashed thread...
qfagent_1::startExecuteMinidumpTaskthread : 2018-04-13-12-41-56-771 : EMT Service started!
qfagent_1::runAssertionHandling : 2018-04-13-12-41-56-771 : Set assertion info in report
PE
qfagent_1::ExecuteMinidumpTaskThread::operator() : 2018-04-13-12-41-56-771 : THE PIPE created
e in worker thread...
qfagent_1::WindowsHandlerState::run : 2018-04-13-12-41-56-772 : Worker thread took over...
qfagent_1::HandlerState::exportCrashInfo : 2018-04-13-12-41-56-772 : Set exception info, thread ID, pid
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-772 : Added context for thread: 0x00000000000033e8
qfagent_1::HandlerState::exportCrashInfo : 2018-04-13-12-41-56-772 : Set thread context
qfagent_1::HandlerState::exportCrashInfo : 2018-04-13-12-41-56-772 : Set crash dump info
qfagent_1::HandlerState::exportCrashInfo : 2018-04-13-12-41-56-775 : Added premortal log
qfagent_1::HandlerState::exportCrashInfo : 2018-04-13-12-41-56-775 : Added app property pool
qfagent_1::ProblemReportStorage::detectProductInfo : 2018-04-13-12-41-56-775 : Detecting product info
qfagent_1::ProblemReportStorage::detectProductInfo : 2018-04-13-12-41-56-775 : failed to derive product info from module map, fallback to cfgmgr API
qfagent_1::HandlerState::exportCrashInfo : 2018-04-13-12-41-56-775 : Set failed product info: Intel(R) VTune(TM) Amplifier 2018 Update 1; 535340
minidump : 2018-04-13-12-41-56-775 : invoke out-of-proc handling...
feedback-tool : 2018-04-13-12-41-56-858 : took over...
wmain : 2018-04-13-12-41-56-859 : Collecting stacks...
collectStacks : 2018-04-13-12-41-56-859 : Entered
collectStacks : 2018-04-13-12-41-56-871 : Loading module map...
collectStacks : 2018-04-13-12-41-56-930 : begin collection stack loop...
collectThreadStack : 2018-04-13-12-41-56-932 : Collecting stack for thread: 0x00000000000013d8
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-937 : Added context for thread: 0x00000000000013d8
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-938 : Added clean stack for thread: 0x00000000000013d8
collectThreadStack : 2018-04-13-12-41-56-938 : Collecting stack for thread: 0x00000000000036cc
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-939 : Added context for thread: 0x00000000000036cc
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-939 : Added clean stack for thread: 0x00000000000036cc
collectThreadStack : 2018-04-13-12-41-56-939 : Collecting stack for thread: 0x0000000000004304
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-940 : Added context for thread: 0x0000000000004304
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-940 : Added clean stack for thread: 0x0000000000004304
collectThreadStack : 2018-04-13-12-41-56-941 : Collecting stack for thread: 0x0000000000003798
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-941 : Added context for thread: 0x0000000000003798
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-941 : Added clean stack for thread: 0x0000000000003798
collectThreadStack : 2018-04-13-12-41-56-941 : Collecting stack for thread: 0x000000000000475c
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-943 : Added context for thread: 0x000000000000475c
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-943 : Added clean stack for thread: 0x000000000000475c
collectThreadStack : 2018-04-13-12-41-56-943 : Collecting stack for thread: 0x0000000000004060
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-944 : Added context for thread: 0x0000000000004060
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-945 : Added clean stack for thread: 0x0000000000004060
collectThreadStack : 2018-04-13-12-41-56-945 : Collecting stack for thread: 0x0000000000003484
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-946 : Added context for thread: 0x0000000000003484
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-947 : Added clean stack for thread: 0x0000000000003484
collectThreadStack : 2018-04-13-12-41-56-947 : Collecting stack for thread: 0x00000000000015d8
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-949 : Added context for thread: 0x00000000000015d8
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-950 : Added clean stack for thread: 0x00000000000015d8
collectThreadStack : 2018-04-13-12-41-56-950 : Collecting stack for thread: 0x00000000000031ec
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-951 : Added context for thread: 0x00000000000031ec
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-952 : Added clean stack for thread: 0x00000000000031ec
collectThreadStack : 2018-04-13-12-41-56-952 : Collecting stack for thread: 0x00000000000033e8
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-956 : Added clean stack for thread: 0x00000000000033e8
collectThreadStack : 2018-04-13-12-41-56-956 : Collecting stack for thread: 0x0000000000004098
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-957 : Added context for thread: 0x0000000000004098
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-957 : Added clean stack for thread: 0x0000000000004098
collectThreadStack : 2018-04-13-12-41-56-957 : Collecting stack for thread: 0x0000000000004018
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-958 : Added context for thread: 0x0000000000004018
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-958 : Added clean stack for thread: 0x0000000000004018
collectThreadStack : 2018-04-13-12-41-56-958 : Collecting stack for thread: 0x00000000000029cc
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-960 : Added context for thread: 0x00000000000029cc
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-960 : Added clean stack for thread: 0x00000000000029cc
collectThreadStack : 2018-04-13-12-41-56-960 : Collecting stack for thread: 0x00000000000011e8
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-962 : Added context for thread: 0x00000000000011e8
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-962 : Added clean stack for thread: 0x00000000000011e8
collectThreadStack : 2018-04-13-12-41-56-962 : Collecting stack for thread: 0x00000000000017a0
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-963 : Added context for thread: 0x00000000000017a0
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-963 : Added clean stack for thread: 0x00000000000017a0
collectThreadStack : 2018-04-13-12-41-56-963 : Collecting stack for thread: 0x0000000000003958
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-964 : Added context for thread: 0x0000000000003958
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-965 : Added clean stack for thread: 0x0000000000003958
collectThreadStack : 2018-04-13-12-41-56-965 : Collecting stack for thread: 0x00000000000032e4
qfagent_1::ProblemReportStorage::addContext : 2018-04-13-12-41-56-967 : Added context for thread: 0x00000000000032e4
qfagent_1::ProblemReportStorage::addStack : 2018-04-13-12-41-56-968 : Added clean stack for thread: 0x00000000000032e4
collectStacks : 2018-04-13-12-41-56-969 : end collection stack loop...
qfagent_1::ProblemReportStorage::SyncModuleMapWithStackMap : 2018-04-13-12-41-56-969 : Sync-up module map with current stack map
qfagent_1::ProblemReportStorage::detectProductInfo : 2018-04-13-12-41-56-970 : Detecting product info
collectStacks : 2018-04-13-12-41-56-972 : added product info
qfagent_1::ProblemReportStorage::updateModuleMap : 2018-04-13-12-41-56-972 : Updating module map...
collectStacks : 2018-04-13-12-41-56-974 : updated module map
collectStacks : 2018-04-13-12-41-56-974 : Finished collecting stacks, exit
wmain : 2018-04-13-12-41-56-974 : Performing intermediate dump of collected stack data
wmain : 2018-04-13-12-41-56-977 : Collecting stacks succeeded
wmain : 2018-04-13-12-41-57-23 : Added report GUID and UUID
qfagent_1::ProblemReportStorage::updateModuleMap : 2018-04-13-12-41-57-65 : Updating module map...
wmain : 2018-04-13-12-41-57-68 : collecting system info...
wmain : 2018-04-13-12-41-59-817 : Appending custom sections

Hi, 

We are using a KNL system running centos Linux. We have installed a trial version of Intel Parallel Studio XE Cluster Edition for Linux on our system. Before trying to run VTune, I loaded the package using this command: "source /opt/intel/bin/compilervars.sh intel64" . Then I tried "amplxe-cl -help" but there was an error that "bash: amplxe-cl: command not found...". I don't know what is going wrong because I think VTune should be already installed and loaded. I will really appreciate your help.

Best, 

Sanaz 

Hi - I am trying to run a system wide profile on a Linux machine that also runs a number of Docker containers. Unfortunately, VTune does not see any of the processes in side the Docker containers, let alone finds any debug information for them. The time spent in those processes is labeled as "Outside any known module" which is a problem as this is 90% of the time.

The processes running inside Docker containers show up in the hosts process list, e.g. using htop I can see them and how much CPU they are consuming. htop shows their command line, and the path to the executables is mapped so it is valid on both host and container. Just VTune ignores them.

I run VTune Amplifier using sudo. No errors are reported before or after performance analysis (except that debug symbols cannot be found for a number of system libraries which is expected).

How can I get this to work? Can I run Docker in a specific mode to is more friendly to profiling?

Thanks for any help.

I cannot run VTune Amplifier both via amplxe-cl and amplxe-gui. Below is the error message if I run via amplxe-cl

I can run via console without any problem and binary is there for sure.

amplxe: Collection started. To stop the collection, either press CTRL-C or enter from another console window: amplxe-cl -r /home/SACCADECAPITAL.LAN/sko/dev/project/r009hs -command stop.
amplxe: Error: Binary file of the analysis target cannot be found. Please check the path or specify another path and try again.
amplxe: Error: [Instrumentation Engine]: /home/SACCADECAPITAL.LAN/sko/dev/project/bin/project_exe : Success

Join the Intel® Parallel Studio XE 2019 Beta Program today and—for a limited time—get early access to new features and get an open invitation to tell us what you really think.

We want YOU to tell us what to improve so we can create high-quality software tools that meet your development needs.

Sign Up Now >

Top New Features in Intel® Parallel Studio XE 2019 Beta

• Scale and perform on the path to exascale. Enable greater scalability and improve latency with the latest Intel^® MPI Library.
• Get better answers with less overhead. Focus more fully on useful data, CPU utilization of physical cores, and more using new data-selection support from Intel^® VTune^™ Amplifier’s Application Performance Snapshot.
• Visualize parallelism. Interactively build, validate, and visualize algorithms using Intel® Advisor’s Flow Graph Analyzer.
• Stay up-to-date with the latest standards:
  • Expanded C++17 and Fortran 2018 support
  • Full OpenMP* 4.5 and expanded OpenMP 5.0 support
  • Python* 3.6 and 2.7

New Features in Intel® VTune™ Amplifier

• New visualization for general exploration results simplifies interpretation of complex counter information, plus new workflow suggestions and analysis groupings simplify setup.
• Application Performance Snapshot – lower overhead, CPU utilization of physical cores and pause/resume to focus on useful data
• Tune SPDK storage and DPDK network [experimental] performance using I/O analysis.  Measure “empty” polling cycles where no real work is done.

To learn more, visit Intel^® Parallel Studio XE 2019 Beta page.

Then sign up to get started.

I was hoping to analyze a performance regression with transform() but when I isolate the case to a single C++ function, VTune says there are no Windows debug symbols created by /debug=inline-debug-info.  Is there a way to solve this, other than to write plain C code?  ICL seems to be reporting vectorization but it acts as if only the remainder loop is executed under a new ICL version.  I don't think it's worth submitting a supporttickets case when the problem can't be isolated and could be solved by avoiding C++.

Hi, recently I followed the vtune tutorial as below to observe the hardware-related issues but I encountered some running error that I cannot figure it out. Hope someone here could give me certain suggestions to resolve it if you have had the same experience before.

https://software.intel.com/en-us/vtuneampxe_hwissues_lin_c

kernel: 3.10.0-514.26.2.el7.x86_64

OS: CentOS 7.3.1611

To collect the event-based metrics, I was asked to install the sampling driver for collecting hardware information as link below mentioned. The installation is very smooth and nothing error.

https://software.intel.com/en-us/vtune-amplifier-help-building-and-installing-the-sampling-drivers-for-linux-targets#GUID-5CCF4158-1740-43B6-8BE5-2D8EB0FB088C

But in vtune tutorial of  General Exploration, the collection log showed me error message as below

"Collection failed. Apr 25 2018 15:08:59 Collection failed. The data cannot be displayed" 

and I have no idea what was wrong with my edition since I just went through all the steps of that tutorial. Does anyone meet the same problem as me? How did you resolve it?

Now I try to follow the tutorial steps for analyzing disk I/O metrics https://software.intel.com/en-us/vtune-amplifier-disk-io-tutorial-linux

But on Analysis Type page it shows error message as below so that I cannot start collection process

"Ftrace collection is not possible due to a lack of credentials. Make sure you have read/write access to debugFS. You may either run the analysis with root privileges (recommended) or follow the configuration instructions provided in the Software Event Library help topic."

For read/write access to debugFS, I typed

$> mount | grep debugfs, and it showed

$> debugfs on /sys/kernel/debug type debugfs (rw, relatime), seems I have read/write access to it, right?

• How to know I have root privileges ? I've been added to the group but same message popped up
• where is the related configuration instruction as message mentioned above (Software Event Library help topic). Could you please share the link with me, thanks. 

Hi All,

Profiling applications running inside the Singularity container is possible with VTune Amplifier. Read an article in VTune Amplifier Performance Analysis Cookbook (https://software.intel.com/en-us/vtune-amplifier-cookbook-profiling-a-java-application-in-a-singularity-container) to get more details.

Your feedback is highly appreciated!

Thanks, Denis

Preface: I ran a General Exploration analysis with "Analyze OpenMP regions" enabled (among others). As I am using MSVC and its associated OpenMP implementation (instead of the Intel one), this has never done anything useful but I did not bother disabling it.

Problem: In the General Exploration Viewpoint, after digging around the profiling results for a while, I decided to see what the Grouping option "OpenMP Region / OpenMP Barrier-to-Barrier Segment / Function / Call Stack" would do. This results in "No data to show" in the grid view. However, it is impossible to change the grouping option when there is "no data to show" - I don't see why this was implemented but in this case it makes me entirely unable to switch to another grouping option to see my results again.

https://i.imgur.com/pQQuhUl.png

For avoidance of doubt: I have plenty of report data that is visible in other grouping modes (e.g. "Function / Call Stack"). I am unable to change the grouping mode, presumably because this grouping mode (and probably any related one) has no data to show.

Neither switching viewpoints (e.g. to Hardware Events and back), nor reloading/reresolving the report, nor restarting VS, nor loading another report changes this. The selected grouping mode appears to be persisted globally. This means I am entirely unable to use the General Exploration Viewpoint's Bottom Up tab in any project.

Please advise on how to restore VTune to functionality, for example by pointing out where the grouping mode is persisted so it can be changed manually. Allowing users to change the grouping mode even with no data to show would also be a welcome change to avoid this issue.

Hi,

I am using Intel VTune 2018 to profile and derive the control flow dependencies by making use of the Intel_PT PMU under the system:

Kernel: 4.15.0-13-generic, 64bit Ubuntu

CPU: Intel® Core™ i7-7820X @ 3.60GHz × 16 

I started with the following commands:

1- amplxe-perf record -o a.perf -T -e intel_pt// -- ps

  PID TTY          TIME CMD
21471 pts/1    00:00:00 amplxe-perf
21472 pts/1    00:00:00 ps
58693 pts/1    00:00:00 sudo
58694 pts/1    00:00:00 su
58695 pts/1    00:00:00 bash
[ perf record: Woken up 2 times to write data ]
[ perf record: Captured and wrote 3.154 MB a.perf ]

2- amplxe-cl -import a.perf -r folder

amplxe: Importing a new result 100 % done                                      
amplxe: Using result path `/home/amad/May2/folder'
amplxe: Executing actions 12 % Loading 'a.perf' file                           
amplxe: Error: Cannot load data file `/home/amad/May2/folder/data.0/a.perf' (Data file is corrupted).
amplxe: Executing actions 50 % done                                            
amplxe: Error: 0x4000001e (Cannot load raw collector data)

Although intel_pt data has not been successfully imported, the data for other kernel PMU events like "cpu-cycles" and "instructions" could be properly handled:

1- amplxe-perf record -o p.perf -T -e cpu-cycles,instructions -- ps

  PID TTY          TIME CMD
 8410 pts/0    00:00:00 sudo
 8458 pts/0    00:00:00 amplxe-perf
 8467 pts/0    00:00:00 ps
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.024 MB p.perf (96 samples) ]

2- amplxe-cl -import p.perf -r r2

amplxe: Importing a new result 100 % done                                      
amplxe: Using result path `/home/amad/r2'
amplxe: Executing actions 19 % Resolving information for `libprocps.so.6.0.0'  
amplxe: Warning: Cannot locate debugging information for file `/lib/x86_64-linux-gnu/libprocps.so.6.0.0'.
amplxe: Executing actions 21 % Resolving information for `vmlinux'             
amplxe: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.
amplxe: Executing actions 75 % Generating a report                             
Collection and Platform Info
----------------------------
Parameter         r2                                  
----------------  ------------------------------------
Operating System  4.15.0-13-generic                   
Computer Name     amad-pc                             
Result Size       2766877                             
Collector Type    Driverless Perf per-process sampling

CPU
---
Parameter          r2        
-----------------  ----------
Frequency          3600000000
Logical CPU Count  16        

Summary
-------
Elapsed Time:             0.011
Paused Time:              0.0  
CPU Time:                 0.011
Average CPU Utilization:  0.897

Event summary
-------------
Hardware Event Type  Hardware Event Count:Self  Hardware Event Sample Count:Self  Events Per Sample
-------------------  -------------------------  --------------------------------  -----------------
cpu-cycles                            40521584                                45  4000             
instructions                          36302909                                51  4000             
amplxe: Executing actions 100 % done

What is wrong with Intel_pt data?

Thanks

I've been doing some instrumentation in my application which logs an immediate value at a fairly high interval.  I've noticed something about how the data is represented in the resulting timeline which I'm trying to understand.

For the purpose of discussion, assume a CSV with data points such as the following:

1126802252083641,3395040,16648,16648

1126802258614980,3281520,16648,16663

1126802346357386,3500640,16648,16648

1126802352506840,3322440,16648,16648

1126802359003661,3292080,16648,16663

1126802446447006,3508560,16648,16648

1126802459008063,3302640,16648,16663

In the default zoom level, these value actual render on the timeline at nearly 2x the values in the CSV (i.e. the graph shows 6.6 million instead of 3.3 million).  If I zoom in further, I start to see values more appropriate (i.e. 3.3 million).

It seems like VTune is somehow accumulating the immediate values.  Is there some maximum reporting interval where I'm not supposed to be generating CSV lines which are too close together in time?  For example, am I only supposed to be able to report one value per millisecond, and if I report more than that it will add the values together?

The data as shown currently is highly misleading and it would be great to better understand how to avoid these issues.  If the answer is something along the lines of "Don't log more than 1 time per X ns/us/ms", then it would be good to know what the threshold is.

Thanks in advance,

Devin Heitmueller

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff}
span.s1 {font-variant-ligatures: no-common-ligatures}

Hi, 

We have a question and we really appreciate your valuable help. The following is a snapshot of VTune Amplifier advanced hotspot analysis bottom-up window . It shows which cores are being used by the threads. Now here is our question: where is the location of these cores on the physical die? We want to see if for example core_0 and core_1 are physically close to each other and share an L2 cache. The same about other pairs of cores. How can we get such information?

Thank you very much

I get "Installing and starting VTSS++ driver...FAILED" when running "./amplxe-sepreg.exe -i" from admin command prompt. How can this be solved? Or is Amplifier not yet compatible with the latest Windows 10 upgrade?