<?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 &amp;gt;...to step through parallel in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Debugging-Functionality-in-Intel-Parallel-Studio-Cluster-Edition/m-p/1034927#M13535</link>
    <description>&lt;P&gt;&amp;gt;...to step through parallel programs and investigate/change individual variable values similar to Gdb...&lt;/P&gt;

&lt;P&gt;No. Inspector is helpful to find issues but can not change variable directly, usually that is post-analysis. When the user modifes source code then recompile it to inspect again.&lt;/P&gt;

&lt;P&gt;However, Inspector has seamless connection to debugger if you add option "-appdebug on-error ", which jumps to GNU debugger GDB* by default.&lt;/P&gt;</description>
    <pubDate>Sat, 01 Aug 2015 00:36:48 GMT</pubDate>
    <dc:creator>Peter_W_Intel</dc:creator>
    <dc:date>2015-08-01T00:36:48Z</dc:date>
    <item>
      <title>Debugging Functionality in Intel Parallel Studio Cluster Edition</title>
      <link>https://community.intel.com/t5/Analyzers/Debugging-Functionality-in-Intel-Parallel-Studio-Cluster-Edition/m-p/1034926#M13534</link>
      <description>&lt;P class="p1"&gt;&lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;I am new to using Intel's Parallel Studio XE Cluster Edition. &amp;nbsp;I am used to using Gdb and Valgrind for debugging. &amp;nbsp;I have just begun using Intel Inspector XE. &amp;nbsp;I was wondering if there is any capability in the Parallel Studio XE Cluster package to step through parallel programs and investigate/change individual variable values similar to Gdb, as well as, step different processors independently? &amp;nbsp;I have not been able to find that functionality as of yet. &amp;nbsp;Thanks!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jul 2015 16:52:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Debugging-Functionality-in-Intel-Parallel-Studio-Cluster-Edition/m-p/1034926#M13534</guid>
      <dc:creator>Ali_S_4</dc:creator>
      <dc:date>2015-07-31T16:52:22Z</dc:date>
    </item>
    <item>
      <title>&gt;...to step through parallel</title>
      <link>https://community.intel.com/t5/Analyzers/Debugging-Functionality-in-Intel-Parallel-Studio-Cluster-Edition/m-p/1034927#M13535</link>
      <description>&lt;P&gt;&amp;gt;...to step through parallel programs and investigate/change individual variable values similar to Gdb...&lt;/P&gt;

&lt;P&gt;No. Inspector is helpful to find issues but can not change variable directly, usually that is post-analysis. When the user modifes source code then recompile it to inspect again.&lt;/P&gt;

&lt;P&gt;However, Inspector has seamless connection to debugger if you add option "-appdebug on-error ", which jumps to GNU debugger GDB* by default.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2015 00:36:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Debugging-Functionality-in-Intel-Parallel-Studio-Cluster-Edition/m-p/1034927#M13535</guid>
      <dc:creator>Peter_W_Intel</dc:creator>
      <dc:date>2015-08-01T00:36:48Z</dc:date>
    </item>
  </channel>
</rss>

