<?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 Memory access error detection in managed code? in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Memory-access-error-detection-in-managed-code/m-p/745390#M1940</link>
    <description>Thanks, that clears it up.</description>
    <pubDate>Tue, 23 Nov 2010 05:27:12 GMT</pubDate>
    <dc:creator>bobcl</dc:creator>
    <dc:date>2010-11-23T05:27:12Z</dc:date>
    <item>
      <title>Memory access error detection in managed code?</title>
      <link>https://community.intel.com/t5/Software-Archive/Memory-access-error-detection-in-managed-code/m-p/745388#M1938</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;
I made a few weeks ago a short evaluation of Intel Parallel Studio.&lt;BR /&gt;&lt;BR /&gt;My test period is over now, but I found rapidly that it does not seem to support memory access errors with C++/CLI managed code, in the same way for example Rational Purify does with non managed code.&lt;BR /&gt;&lt;BR /&gt;
Here is the simple test program I tried:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
void main()&lt;BR /&gt;
{&lt;BR /&gt;&lt;BR /&gt;
 char *foo;&lt;BR /&gt;
 int i;&lt;BR /&gt;&lt;BR /&gt;
 foo = (char *) malloc(10);&lt;BR /&gt;
 for (i = 0; i&amp;lt;10; i++)&lt;BR /&gt;
 foo&lt;I&gt; = 'a';&lt;BR /&gt;
 foo&lt;I&gt; = '\\0';&lt;BR /&gt;
 foo[-1] = '\\0';&lt;BR /&gt;&lt;BR /&gt;
}&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
No error was reported here.&lt;BR /&gt;&lt;BR /&gt;
Did I miss something, or is Intel Parallel Studio unable to detect in real time this kind of errors?&lt;BR /&gt;&lt;P&gt;I tested several other tools, and none so far is able to do so with managed code.&lt;/P&gt;&lt;/I&gt;&lt;/I&gt;</description>
      <pubDate>Mon, 22 Nov 2010 12:42:52 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Memory-access-error-detection-in-managed-code/m-p/745388#M1938</guid>
      <dc:creator>bobcl</dc:creator>
      <dc:date>2010-11-22T12:42:52Z</dc:date>
    </item>
    <item>
      <title>Memory access error detection in managed code?</title>
      <link>https://community.intel.com/t5/Software-Archive/Memory-access-error-detection-in-managed-code/m-p/745389#M1939</link>
      <description>&lt;P&gt;IntelParallel Inspector 2011 does not work on C++ .NET managed code. It does work on C++ native binaries as described in the System Requirements: &lt;A href="http://software.intel.com/sites/products/documentation/studio/inspector/en-us/2011/start/release_notes_inspector.pdf" target="_blank"&gt;http://software.intel.com/sites/products/documentation/studio/inspector/en-us/2011/start/release_notes_inspector.pdf&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Programming Language: C or C++ (native, not managed code) [0]&lt;/P&gt;&lt;P&gt;Intel Parallel Inspector 2011 will also find memory and threading errors in the unmanaged code of a mixed mode binary.&lt;/P&gt;&lt;P&gt;Our New Product: Intel Inspector XE 2011will additonally find threading errors on C#.NET managed code.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Eric M&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2010 23:32:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Memory-access-error-detection-in-managed-code/m-p/745389#M1939</guid>
      <dc:creator>Eric_M_Intel2</dc:creator>
      <dc:date>2010-11-22T23:32:45Z</dc:date>
    </item>
    <item>
      <title>Memory access error detection in managed code?</title>
      <link>https://community.intel.com/t5/Software-Archive/Memory-access-error-detection-in-managed-code/m-p/745390#M1940</link>
      <description>Thanks, that clears it up.</description>
      <pubDate>Tue, 23 Nov 2010 05:27:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Memory-access-error-detection-in-managed-code/m-p/745390#M1940</guid>
      <dc:creator>bobcl</dc:creator>
      <dc:date>2010-11-23T05:27:12Z</dc:date>
    </item>
  </channel>
</rss>

