<?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 Alternative to Intel Inspector? in Intel® oneAPI DPC++/C++ Compiler</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1625535#M4059</link>
    <description>&lt;P&gt;Not directly related to C/C++ but I have always used Intel Inspector for many years on both Windows and Linux to track tricky threading and memory access issues.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Now that it is being retired, what alternatives do people have? Particularly on Windows. Looking for a tool that does not required the code to be recompiled.&lt;BR /&gt;&lt;BR /&gt;On Linux, valgrind is "OK", but it suffers from being open source, and the lack of a GUI makes it painful to use.&lt;/P&gt;</description>
    <pubDate>Fri, 23 Aug 2024 18:38:19 GMT</pubDate>
    <dc:creator>AndrewC</dc:creator>
    <dc:date>2024-08-23T18:38:19Z</dc:date>
    <item>
      <title>Alternative to Intel Inspector?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1625535#M4059</link>
      <description>&lt;P&gt;Not directly related to C/C++ but I have always used Intel Inspector for many years on both Windows and Linux to track tricky threading and memory access issues.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Now that it is being retired, what alternatives do people have? Particularly on Windows. Looking for a tool that does not required the code to be recompiled.&lt;BR /&gt;&lt;BR /&gt;On Linux, valgrind is "OK", but it suffers from being open source, and the lack of a GUI makes it painful to use.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Aug 2024 18:38:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1625535#M4059</guid>
      <dc:creator>AndrewC</dc:creator>
      <dc:date>2024-08-23T18:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative to Intel Inspector?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1626014#M4061</link>
      <description>&lt;P&gt;Please try sanitizer:&amp;nbsp;&lt;A href="https://www.intel.com/content/www/us/en/developer/articles/technical/find-bugs-quickly-using-sanitizers-with-oneapi-compiler.html" target="_blank"&gt;https://www.intel.com/content/www/us/en/developer/articles/technical/find-bugs-quickly-using-sanitizers-with-oneapi-compiler.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Aug 2024 08:12:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1626014#M4061</guid>
      <dc:creator>Alex_Y_Intel</dc:creator>
      <dc:date>2024-08-26T08:12:12Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative to Intel Inspector?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1626154#M4062</link>
      <description>&lt;P&gt;My comments&lt;BR /&gt;- it requires the code be recompiled with new options - another special build.&lt;/P&gt;&lt;P&gt;- I used Intel Inspector for diagnosing tricky threading issues, not just memory issues.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Aug 2024 17:31:20 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1626154#M4062</guid>
      <dc:creator>AndrewC</dc:creator>
      <dc:date>2024-08-26T17:31:20Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative to Intel Inspector?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1626197#M4063</link>
      <description>&lt;P&gt;Sanitizer is able to do the thread checking too, suppose you have a source code tiny_race.cpp:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;icpx -fsanitize=thread -g tiny_race.cpp&lt;BR /&gt;icpx: remark: Note that use of '-g' without any optimization-level option will turn off most compiler optimizations similar to use of '-O0'; use '-Rno-debug-disables-optimization' to disable this remark [-Rdebug-disables-optimization]&lt;BR /&gt;sravanik@ortce-skl22:~$ ./a.out&lt;BR /&gt;==================&lt;BR /&gt;WARNING: ThreadSanitizer: data race (pid=1974537)&lt;BR /&gt;&amp;nbsp; Write of size 4 at 0x000001913ae8 by main thread:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; #0 main /nfs/pdx/home/tiny_race.cpp:10:10 (a.out+0x4e57de)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Previous write of size 4 at 0x000001913ae8 by thread T1:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; #0 Thread1(void*) /nfs/pdx/home/tiny_race.cpp:4:10 (a.out+0x4e577b)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Location is global 'Global' of size 4 at 0x000001913ae8 (a.out+0x1913ae8)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Thread T1 (tid=1974557, finished) created by main thread at:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; #0 pthread_create &amp;lt;null&amp;gt; (a.out+0x436463)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; #1 main /nfs/pdx/home/tiny_race.cpp:9:3 (a.out+0x4e57d4)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SUMMARY: ThreadSanitizer: data race /nfs/pdx/home/tiny_race.c:10:10 in main&lt;BR /&gt;==================&lt;BR /&gt;ThreadSanitizer: reported 1 warnings&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Aug 2024 20:58:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Alternative-to-Intel-Inspector/m-p/1626197#M4063</guid>
      <dc:creator>Alex_Y_Intel</dc:creator>
      <dc:date>2024-08-26T20:58:33Z</dc:date>
    </item>
  </channel>
</rss>

