<?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 Inspector 2013 for WINDOWS to debug mingw-gcc compiled code in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Inspector-2013-for-WINDOWS-to-debug-mingw-gcc-compiled-code/m-p/988239#M10632</link>
    <description>Can code compiled with mingw-gcc on windows be analyzed using Inspector?
Does the intel debugger recozgnize gdb debugging symbols?
Does the code need to be compiled with specific debug switches (-ggdb, -g-dwarf2 etc.)?

Thanks,</description>
    <pubDate>Fri, 11 Jan 2013 20:51:27 GMT</pubDate>
    <dc:creator>sigmahat</dc:creator>
    <dc:date>2013-01-11T20:51:27Z</dc:date>
    <item>
      <title>Inspector 2013 for WINDOWS to debug mingw-gcc compiled code</title>
      <link>https://community.intel.com/t5/Analyzers/Inspector-2013-for-WINDOWS-to-debug-mingw-gcc-compiled-code/m-p/988239#M10632</link>
      <description>Can code compiled with mingw-gcc on windows be analyzed using Inspector?
Does the intel debugger recozgnize gdb debugging symbols?
Does the code need to be compiled with specific debug switches (-ggdb, -g-dwarf2 etc.)?

Thanks,</description>
      <pubDate>Fri, 11 Jan 2013 20:51:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Inspector-2013-for-WINDOWS-to-debug-mingw-gcc-compiled-code/m-p/988239#M10632</guid>
      <dc:creator>sigmahat</dc:creator>
      <dc:date>2013-01-11T20:51:27Z</dc:date>
    </item>
    <item>
      <title>Sorry that code compiled with</title>
      <link>https://community.intel.com/t5/Analyzers/Inspector-2013-for-WINDOWS-to-debug-mingw-gcc-compiled-code/m-p/988240#M10633</link>
      <description>&lt;P&gt;Sorry that code compiled with minggw-cc is NOT supported for both Inspector XE and VTune(TM) Amplifier XE, for now.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2013 06:48:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Inspector-2013-for-WINDOWS-to-debug-mingw-gcc-compiled-code/m-p/988240#M10633</guid>
      <dc:creator>Peter_W_Intel</dc:creator>
      <dc:date>2013-01-14T06:48:37Z</dc:date>
    </item>
    <item>
      <title>Even on linux, where gcc and</title>
      <link>https://community.intel.com/t5/Analyzers/Inspector-2013-for-WINDOWS-to-debug-mingw-gcc-compiled-code/m-p/988241#M10634</link>
      <description>&lt;P&gt;Even on linux, where gcc and icc use the same debug symbol formats, Inspector instructions specify that Intel compilers must be used. If you can generate debug symbols compatible with Visual Studio debugger, it may be worth trying.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Feb 2013 02:40:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Inspector-2013-for-WINDOWS-to-debug-mingw-gcc-compiled-code/m-p/988241#M10634</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2013-02-01T02:40:33Z</dc:date>
    </item>
  </channel>
</rss>

