<?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 Re: Parallel Inspector: uninitialized memory access, more infor in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Parallel-Inspector-uninitialized-memory-access-more-information/m-p/742346#M944</link>
    <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;BR /&gt; Sure just having it in the detailled report after a double click would certainly be enough for me.&lt;BR /&gt;&lt;BR /&gt;Laurent,&lt;BR /&gt;</description>
    <pubDate>Wed, 01 Apr 2009 07:46:13 GMT</pubDate>
    <dc:creator>LLess</dc:creator>
    <dc:date>2009-04-01T07:46:13Z</dc:date>
    <item>
      <title>Parallel Inspector: uninitialized memory access, more information would be welcome.</title>
      <link>https://community.intel.com/t5/Software-Archive/Parallel-Inspector-uninitialized-memory-access-more-information/m-p/742344#M942</link>
      <description>Hi guys,&lt;BR /&gt;&lt;BR /&gt;I think having the base pointer and memory allocation size as well as the pointer where the unitialized access occurs would help.&lt;BR /&gt;Obviously you must have the information internally so it would just be a matter of displaying it somewhere in the error report.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Fri, 27 Feb 2009 04:55:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Parallel-Inspector-uninitialized-memory-access-more-information/m-p/742344#M942</guid>
      <dc:creator>LLess</dc:creator>
      <dc:date>2009-02-27T04:55:45Z</dc:date>
    </item>
    <item>
      <title>Re: Parallel Inspector: uninitialized memory access, more infor</title>
      <link>https://community.intel.com/t5/Software-Archive/Parallel-Inspector-uninitialized-memory-access-more-information/m-p/742345#M943</link>
      <description>&lt;DIV style="margin: 0px; height: auto;"&gt;&lt;/DIV&gt;
&lt;DIV style="margin:0px;"&gt;That is a nice suggestion, Laurent. Let me take it to Engineering and see what we can come up with. We have found that overloading information in a column is confusing, and we do not want to add too many columns which will complicate the interface.&lt;BR /&gt;&lt;BR /&gt;Do note that the allocation point (if heap allocated) is shown as a related observation, so the information is available with a couple of clicks.&lt;BR /&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 12 Mar 2009 15:28:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Parallel-Inspector-uninitialized-memory-access-more-information/m-p/742345#M943</guid>
      <dc:creator>Jayant_D_Intel</dc:creator>
      <dc:date>2009-03-12T15:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: Parallel Inspector: uninitialized memory access, more infor</title>
      <link>https://community.intel.com/t5/Software-Archive/Parallel-Inspector-uninitialized-memory-access-more-information/m-p/742346#M944</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;BR /&gt; Sure just having it in the detailled report after a double click would certainly be enough for me.&lt;BR /&gt;&lt;BR /&gt;Laurent,&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Apr 2009 07:46:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Parallel-Inspector-uninitialized-memory-access-more-information/m-p/742346#M944</guid>
      <dc:creator>LLess</dc:creator>
      <dc:date>2009-04-01T07:46:13Z</dc:date>
    </item>
  </channel>
</rss>

