<?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: crash when running activity (call graph) in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989819#M10832</link>
    <description>hi, &lt;BR /&gt;you are righ; the debug info manipulations are important to get meaningful information from VTune collections, espessially in call graph.&lt;BR /&gt;you are also right that you use release configuration as a base and change there some flags.&lt;BR /&gt;&lt;BR /&gt;i do it in 2 places :&lt;BR /&gt;1) in C/C++ tab I put "Debug info" to "program database"&lt;BR /&gt;2) in Linker tab I mark "Debug Info" check box + /fixed:no. &lt;BR /&gt;I never generate MAP files. Is there anything specific with them that you need?&lt;BR /&gt;&lt;BR /&gt;Please try this configuration. Does it help?&lt;BR /&gt;&lt;BR /&gt;Anyway you can use Premier Intel Support to submit your issue, even if you have an eval version.&lt;BR /&gt;&lt;BR /&gt;-Daniel</description>
    <pubDate>Sat, 10 May 2003 13:32:45 GMT</pubDate>
    <dc:creator>Daniel_B_Intel2</dc:creator>
    <dc:date>2003-05-10T13:32:45Z</dc:date>
    <item>
      <title>crash when running activity (call graph)</title>
      <link>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989818#M10831</link>
      <description>I have a DirectX application. It's a cloth simulation. The debug and release version run fine. I did this before:&lt;BR /&gt;-Set to Release&lt;BR /&gt;-Linker-&amp;gt;Command Line, Add "/fixed:no" &lt;BR /&gt;-Linker-&amp;gt;Debug, &lt;BR /&gt;	-Turn "Generate Debug Info" to "Yes(/DEBUG)"&lt;BR /&gt;	-Turn "Generate Map File" to "Yes(/MAP)"	&lt;BR /&gt;	-Turn "Map Exports" to "Yes(/MAPINFO:EXPORTS)"&lt;BR /&gt;&lt;BR /&gt;It works fine with the a sample DirectX program that comes with the SDK. But with mine, it crashes right at the beginning.&lt;BR /&gt;&lt;BR /&gt;I'm running the eval version. If I fix the problem I will buy it. But right not it seems using high performance counters will be the solution.&lt;BR /&gt;&lt;BR /&gt;Thanks if you can help me!</description>
      <pubDate>Sat, 10 May 2003 03:01:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989818#M10831</guid>
      <dc:creator>matthieugp</dc:creator>
      <dc:date>2003-05-10T03:01:54Z</dc:date>
    </item>
    <item>
      <title>Re: crash when running activity (call graph)</title>
      <link>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989819#M10832</link>
      <description>hi, &lt;BR /&gt;you are righ; the debug info manipulations are important to get meaningful information from VTune collections, espessially in call graph.&lt;BR /&gt;you are also right that you use release configuration as a base and change there some flags.&lt;BR /&gt;&lt;BR /&gt;i do it in 2 places :&lt;BR /&gt;1) in C/C++ tab I put "Debug info" to "program database"&lt;BR /&gt;2) in Linker tab I mark "Debug Info" check box + /fixed:no. &lt;BR /&gt;I never generate MAP files. Is there anything specific with them that you need?&lt;BR /&gt;&lt;BR /&gt;Please try this configuration. Does it help?&lt;BR /&gt;&lt;BR /&gt;Anyway you can use Premier Intel Support to submit your issue, even if you have an eval version.&lt;BR /&gt;&lt;BR /&gt;-Daniel</description>
      <pubDate>Sat, 10 May 2003 13:32:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989819#M10832</guid>
      <dc:creator>Daniel_B_Intel2</dc:creator>
      <dc:date>2003-05-10T13:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: crash when running activity (call graph)</title>
      <link>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989820#M10833</link>
      <description>I did this but I still have the same problem. I don't think it is useful but after it crashes I get a window titled: "The following EXEs or DLLs were dynamically loaded but not instrumented"&lt;BR /&gt;c:WINDOWSsystem32dwwin.exe&lt;BR /&gt;&lt;BR /&gt;It's as if there is something in my exe VTune doesn't like. Ouch!&lt;BR /&gt;&lt;BR /&gt;Matthieu</description>
      <pubDate>Mon, 12 May 2003 08:29:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989820#M10833</guid>
      <dc:creator>matthieugp</dc:creator>
      <dc:date>2003-05-12T08:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: crash when running activity (call graph)</title>
      <link>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989821#M10834</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Is it possible to share this application or at least a minimal example to reproduce the crash?&lt;BR /&gt;&lt;BR /&gt;If 'yes', please describe your environment in details:&lt;BR /&gt;- Hardware platform&lt;BR /&gt;- OS&lt;BR /&gt;- installed SDK-s and IDE-s&lt;BR /&gt;- what do you use to build the application&lt;BR /&gt;- VTune analyzer version and the source you took it from&lt;BR /&gt;&lt;BR /&gt;Probably we will be able to invent some kind of workaround and help you.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;Konstantin Lupach&lt;BR /&gt;&lt;BR /&gt;P.S. &lt;BR /&gt;you can send the app directly to me if its small in size (~1mb).&lt;BR /&gt;however, the preferred way is to put the sources, binaries and symbol files to a ftp site and provide a link.</description>
      <pubDate>Mon, 12 May 2003 14:03:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989821#M10834</guid>
      <dc:creator>Konstantin_L_Intel</dc:creator>
      <dc:date>2003-05-12T14:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: crash when running activity (call graph)</title>
      <link>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989822#M10835</link>
      <description>You can try playing with the Call Graph advanced configuration and lower the instrumentation level of certain DLL groups, to see if it helps.&lt;BR /&gt;&lt;BR /&gt;- Try disabling COM Tracing&lt;BR /&gt;- Try &lt;I&gt;Minimal&lt;/I&gt; instrumentation for System DLLs, and for User DLLs.&lt;BR /&gt;&lt;BR /&gt;Hope it helps,&lt;BR /&gt;Boaz.</description>
      <pubDate>Fri, 16 May 2003 02:03:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989822#M10835</guid>
      <dc:creator>Intel_C_Intel</dc:creator>
      <dc:date>2003-05-16T02:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: crash when running activity (call graph)</title>
      <link>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989823#M10836</link>
      <description>the problem was in the app itself -- it has to be run from its root directory, otherwise it crashes.</description>
      <pubDate>Tue, 20 May 2003 10:49:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/crash-when-running-activity-call-graph/m-p/989823#M10836</guid>
      <dc:creator>Konstantin_L_Intel</dc:creator>
      <dc:date>2003-05-20T10:49:32Z</dc:date>
    </item>
  </channel>
</rss>

