<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Very slow execution Inspector Linux in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Very-slow-execution-Inspector-Linux/m-p/1150634#M17407</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm using Intel(R) Inspector 2017 Update 1 (build 484836) Command Line tool to find a memory corruption an application server, but I can't finish the test with inspector because it take a lot of time, about hours for single execution.&lt;/P&gt;

&lt;P&gt;I try to use the collection-with option and with this option just test for leaks problems and don't to memory access problems.&lt;/P&gt;

&lt;P&gt;Below is some line commands that i try, just the # 2 end the execution.&lt;/P&gt;

&lt;P&gt;1) inspxe-cl --collect mi3 -- /home/fg/p11/bin/appserverx64/appsrvlinux&lt;/P&gt;

&lt;P&gt;2) nspxe-cl -collect-with runmc -knob enable-memory-growth-detection=false -knob enable-guard-zones=true -knob enable-on-demand-leak-detection=false -knob detect-leaks-on-exit=false&amp;nbsp; -- /home/fg/p11/bin/appserverx64/appsrvlinux&lt;/P&gt;

&lt;P&gt;3) inspxe-cl -collect mi2 -knob enable-on-demand-leak-detection=false -- /home/fg/p11/bin/appserverx64/appsrvlinux&lt;/P&gt;

&lt;P&gt;Is there some option to just run memory access problems ?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 08 Mar 2018 14:14:27 GMT</pubDate>
    <dc:creator>Garbin__Fabio</dc:creator>
    <dc:date>2018-03-08T14:14:27Z</dc:date>
    <item>
      <title>Very slow execution Inspector Linux</title>
      <link>https://community.intel.com/t5/Analyzers/Very-slow-execution-Inspector-Linux/m-p/1150634#M17407</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm using Intel(R) Inspector 2017 Update 1 (build 484836) Command Line tool to find a memory corruption an application server, but I can't finish the test with inspector because it take a lot of time, about hours for single execution.&lt;/P&gt;

&lt;P&gt;I try to use the collection-with option and with this option just test for leaks problems and don't to memory access problems.&lt;/P&gt;

&lt;P&gt;Below is some line commands that i try, just the # 2 end the execution.&lt;/P&gt;

&lt;P&gt;1) inspxe-cl --collect mi3 -- /home/fg/p11/bin/appserverx64/appsrvlinux&lt;/P&gt;

&lt;P&gt;2) nspxe-cl -collect-with runmc -knob enable-memory-growth-detection=false -knob enable-guard-zones=true -knob enable-on-demand-leak-detection=false -knob detect-leaks-on-exit=false&amp;nbsp; -- /home/fg/p11/bin/appserverx64/appsrvlinux&lt;/P&gt;

&lt;P&gt;3) inspxe-cl -collect mi2 -knob enable-on-demand-leak-detection=false -- /home/fg/p11/bin/appserverx64/appsrvlinux&lt;/P&gt;

&lt;P&gt;Is there some option to just run memory access problems ?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 14:14:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Very-slow-execution-Inspector-Linux/m-p/1150634#M17407</guid>
      <dc:creator>Garbin__Fabio</dc:creator>
      <dc:date>2018-03-08T14:14:27Z</dc:date>
    </item>
    <item>
      <title> </title>
      <link>https://community.intel.com/t5/Analyzers/Very-slow-execution-Inspector-Linux/m-p/1150635#M17408</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Yes.... we have api's that allow you to control what portions of your app are analyzed.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://software.intel.com/en-us/inspector-user-guide-linux-apis-for-collection-control"&gt;https://software.intel.com/en-us/inspector-user-guide-linux-apis-for-collection-control&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The main recommendation I would give is to try to analyze on the smallest subset of the problem that you can.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 15:03:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Very-slow-execution-Inspector-Linux/m-p/1150635#M17408</guid>
      <dc:creator>Kevin_O_Intel1</dc:creator>
      <dc:date>2018-03-08T15:03:12Z</dc:date>
    </item>
  </channel>
</rss>

