Analyzers
Community support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)
4969 Discussions

Intel Xeon Phi Intel Inspector analisys

H__Kamil
Beginner
495 Views

Hi. I have problem with analysis my aplication on Intel Xeon Phi. After analisys in result list i havent full information about problem. I use Intel Inspector xe 2015.

First: I compile program on host, with flags: icc -g -O0 -mmic ... -o main.cpp main.out

Second: After compilation I copy program to Intel Xeon Phi: scp ./main.out mic0:/tmp

Third: I create project. As Aplication i type ssh, as Aplication Parameters i type: mic0 '/tmp/matrix.out'

After do this, i run detect memory leak analisys and in result i get list of error, but without information about line of code that causes error. During the analysis, I see int terminal that the application do calculations.

Where is problem? Thanks.

0 Kudos
3 Replies
Peter_W_Intel
Employee
495 Views

I don't know how did you run Inspector on Intel(R) Xeon(R) Phi(TM) processor on your side.

I gave you my example, and result was expected:

# icc -g -O0 -mmic test_memory.c -o test_memory.MIC
# scp test_memory.MIC mic0:/root
test_memory.MIC                               100%   12KB  11.5KB/s   00:00    
# ssh mic0 /root/test_memory.MIC
test leak
test uninitialized
test overlap memory copy

# inspxe-cl -collect mi3 -- ssh mic0 /root/test_memory.MIC
test leak
test uninitialized
test overlap memory copy
  
5 new problem(s) found 
    2 Invalid partial memory access problem(s) detected 
    2 Memory leak problem(s) detected 
    1 Memory not deallocated problem(s) detected 

# inspxe-cl -version
Intel(R) Inspector XE 2015 Update 1 (build 379161) Command Line tool
Copyright (C) 2009-2014 Intel Corporation. All rights reserved.

0 Kudos
Mark_D_Intel
Employee
495 Views

This runs 'ssh' under IXE, not the MIC executable.

IXE does not currently support Xeon Phi executables directly.   To analyze the executable with IXE,  compile for (and run on) the host processor instead.

0 Kudos
Peter_W_Intel
Employee
495 Views

Mark is right. The problem was located at ssh module.

# inspxe-cl -finalize --search-dir all:rp=. -r r001mi3/
  
5 new problem(s) found 
    2 Invalid partial memory access problem(s) detected 
    2 Memory leak problem(s) detected 
    1 Memory not deallocated problem(s) detected 

# inspxe-cl -report problems
P1: Error: Memory leak: New
 P1.15: Error: Memory leak: 38 Bytes: New
  ssh!0x3217d: Error X22: Allocation site: Function [Unknown]: Module /usr/bin/ssh

 

 

0 Kudos
Reply