Community
cancel
Showing results for 
Search instead for 
Did you mean: 
kwak__joonyoung
Beginner
163 Views

Intel System Studio Inspector problems

Hi,

I tested the inspector 2019 in the Ubuntu 16.04.

However, I have a problem.

 

I inspected the my app using the memory error analysis on the inspector 2019.

The "Detect Leaks" level in the Memory Error Analysis is operated normally.

However, the "Detect Memory Problems" and the "Locate Memory Problems" levels display the errors.

The error logs are follow as.

 

* GUI

Error detected during analysis

An internal error has occurred. Our apologies for this inconvenience. Please gather a description of the steps leading up to the problem and contact the intel customer support teams.

 

Analysis completed

Inspector encountered an error during analysis. Check the Collector Messages pane for details.

 

* Collector Messages

Analysis started...
Result file: /home/cvpr0502/intel/inspxe/projects/inspector_002/r001mi3/r001mi3.inspxe
Analysis started for /home/cvpr0502/Projects/NMSS/Tasks/NMSS/Build/NMSSMultiLive (pid = 27799)
Loaded module: /home/cvpr0502/Projects/NMSS/Tasks/NMSS/Build/NMSSMultiLive, address range [0x400000-0x39dc29f]
Loaded module: /lib64/ld-linux-x86-64.so.2, address range [0x7fbaeabc5000-0x7fbaeadec167], minimal analysis
Loaded module: [vdso], address range [0x7ffea77ce000-0x7ffea77cf01a]
Loaded module: /lib/x86_64-linux-gnu/librt.so.1, address range [0x7fbad6106000-0x7fbad630dbbf]
Loaded module: /lib/x86_64-linux-gnu/libresolv.so.2, address range [0x7fbad5e3b000-0x7fbad6055a47]
Loaded module: /lib/x86_64-linux-gnu/libpthread.so.0, address range [0x7fbad5c1e000-0x7fbad5e3a427]
Loaded module: /lib/x86_64-linux-gnu/libdl.so.2, address range [0x7fbad5a0d000-0x7fbad5c100ef], minimal analysis
Loaded module: /usr/lib/x86_64-linux-gnu/libstdc++.so.6, address range [0x7fbad5650000-0x7fbad59d13ff]
Loaded module: /lib/x86_64-linux-gnu/libm.so.6, address range [0x7fbad5347000-0x7fbad564f0f7]
Loaded module: /lib/x86_64-linux-gnu/libgcc_s.so.1, address range [0x7fbad5121000-0x7fbad533690f]
Loaded module: /lib/x86_64-linux-gnu/libc.so.6, address range [0x7fbad4d2d000-0x7fbad50f699f]
Error: An internal error has occurred. Our apologies for this inconvenience. Please gather a description of the steps leading up to the problem and contact the Intel customer support team.
Application exit code: 255
Result file: /home/cvpr0502/intel/inspxe/projects/inspector_002/r001mi3/r001mi3.inspxe
Analysis completed

 

* /r001mi3/data.o/inspxe-runmc.log file

<?xml version="1.0" encoding="utf-8"?>
<log version="1.0" tool="runtool">

<msg id="1" tool="runtool">
  <type>log-start</type>
  <arg>2019/02/19 20:08:42</arg>
</msg>
<msg id="2" tool="runtool">
  <type>collector-starts</type>
</msg>
<msg id="3" tool="runtool">
  <type>marker-file</type>
  <arg>/home/cvpr0502/intel/inspxe/projects/inspector_002/r001mi3/r001mi3.inspxe</arg>
</msg>
<msg id="4" tool="mc">
  <type>EXEC_OF_INTEREST</type>
  <arg>/home/cvpr0502/Projects/NMSS/Tasks/NMSS/Build/NMSSMultiLive</arg>
  <arg>27799</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:42 2019</timestamp>
</msg>
<msg id="5" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>/home/cvpr0502/Projects/NMSS/Tasks/NMSS/Build/NMSSMultiLive</arg>
  <arg>0x400000</arg>
  <arg>0x39dc29f</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="6" tool="mc">
  <type>MODULE_LOAD_NO_ANALYSIS</type>
  <arg>/lib64/ld-linux-x86-64.so.2</arg>
  <arg>0x7fbaeabc5000</arg>
  <arg>0x7fbaeadec167</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="7" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>[vdso]</arg>
  <arg>0x7ffea77ce000</arg>
  <arg>0x7ffea77cf01a</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="8" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>/lib/x86_64-linux-gnu/librt.so.1</arg>
  <arg>0x7fbad6106000</arg>
  <arg>0x7fbad630dbbf</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="9" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>/lib/x86_64-linux-gnu/libresolv.so.2</arg>
  <arg>0x7fbad5e3b000</arg>
  <arg>0x7fbad6055a47</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="10" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>/lib/x86_64-linux-gnu/libpthread.so.0</arg>
  <arg>0x7fbad5c1e000</arg>
  <arg>0x7fbad5e3a427</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="11" tool="mc">
  <type>MODULE_LOAD_NO_ANALYSIS</type>
  <arg>/lib/x86_64-linux-gnu/libdl.so.2</arg>
  <arg>0x7fbad5a0d000</arg>
  <arg>0x7fbad5c100ef</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="12" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>/usr/lib/x86_64-linux-gnu/libstdc++.so.6</arg>
  <arg>0x7fbad5650000</arg>
  <arg>0x7fbad59d13ff</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="13" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>/lib/x86_64-linux-gnu/libm.so.6</arg>
  <arg>0x7fbad5347000</arg>
  <arg>0x7fbad564f0f7</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="14" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>/lib/x86_64-linux-gnu/libgcc_s.so.1</arg>
  <arg>0x7fbad5121000</arg>
  <arg>0x7fbad533690f</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="15" tool="mc">
  <type>MODULE_LOAD</type>
  <arg>/lib/x86_64-linux-gnu/libc.so.6</arg>
  <arg>0x7fbad4d2d000</arg>
  <arg>0x7fbad50f699f</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:44 2019</timestamp>
</msg>
<msg id="16" tool="mc">
  <type>HEARTBEAT</type>
  <arg>27799</arg>
  <arg>0</arg>
  <arg>16627</arg>
  <severity>INFO</severity>
  <timestamp>Tue Feb 19 20:08:45 2019</timestamp>
</msg>
<msg id="17" tool="pin">
  <type>2</type>
  <description>Source/pin/vm/current_location_recorder.cpp: Record: 164: assertion failed: bbl != BBL_INVALID() </description>
  <severity>ERROR</severity>
  <timestamp>Tue Feb 19 20:08:45 2019 </timestamp>
  <pinversion>3.6</pinversion>
  <kitnumber>97585</kitnumber>
</msg>
<msg id="18" tool="runtool">
  <type>app-exit-code</type>
  <arg>255</arg>
</msg>
<msg id="19" tool="runtool">
  <type>marker-file</type>
  <arg>/home/cvpr0502/intel/inspxe/projects/inspector_002/r001mi3/r001mi3.inspxe</arg>
</msg>
<msg id="20" tool="runtool">
  <type>collector-done</type>
</msg>
<msg id="21" tool="runtool">
  <type>log-end</type>
  <arg>2019/02/19 20:08:49</arg>
</msg>

</log>

 

* /r001mi3/data.0/pin.log file

Pin: pin-3.6-97585-7f3412109
Copyright (c) 2003-2018, Intel Corporation. All rights reserved.
A:  Source/pin/vm/current_location_recorder.cpp: Record: 164: assertion failed: bbl != BBL_INVALID()

 

* /r001mi3/data.0/pin_error.log file

<?xml version="1.0" encoding="utf-8" ?>
<!--  DO NOT EDIT THIS FILE -->
<log version="2.0" source="pin">
<msg id="1">
<type>2</type>
<description>Source/pin/vm/current_location_recorder.cpp: Record: 164: assertion failed: bbl != BBL_INVALID() </description>
<severity>ERROR</severity>
<timestamp>Tue Feb 19 20:08:45 2019 </timestamp>
<pinversion>3.6</pinversion>
<kitnumber>97585</kitnumber>
</msg>
</log>

 

Please the answer the how to resolve the error.

Thanks for any pointers to resolving this.

0 Kudos
1 Reply
Sergey_K_Intel3
Employee
163 Views

Can you please open a ticket at Intel's Online Service Center (https://supporttickets.intel.com/?lang=en-US) and attach the binary/test case to help us reproduce this issue?

 

Thanks,

Sergey

Reply