<?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 Core file equivalent on Windows in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839018#M57011</link>
    <description>I'm running large distributed parallel jobs.  Due to the nature of the jobs, it is often not feasible to attach a debugger to a running job, or to run a task in the debugger. &lt;BR /&gt;&lt;BR /&gt;One debugging tool that is useful in the Unix world is the core file.  If a parallel task crashes, you get a core dump that can be analyzed in the debugger.  The most important information (available even in executables built without debug) is the stack trace at the time of the crash.  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Is there a way to get equivalent functionality using Visal Fortran?</description>
    <pubDate>Fri, 18 Oct 2002 08:37:35 GMT</pubDate>
    <dc:creator>bradlepc</dc:creator>
    <dc:date>2002-10-18T08:37:35Z</dc:date>
    <item>
      <title>Core file equivalent on Windows</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839018#M57011</link>
      <description>I'm running large distributed parallel jobs.  Due to the nature of the jobs, it is often not feasible to attach a debugger to a running job, or to run a task in the debugger. &lt;BR /&gt;&lt;BR /&gt;One debugging tool that is useful in the Unix world is the core file.  If a parallel task crashes, you get a core dump that can be analyzed in the debugger.  The most important information (available even in executables built without debug) is the stack trace at the time of the crash.  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Is there a way to get equivalent functionality using Visal Fortran?</description>
      <pubDate>Fri, 18 Oct 2002 08:37:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839018#M57011</guid>
      <dc:creator>bradlepc</dc:creator>
      <dc:date>2002-10-18T08:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Core file equivalent on Windows</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839019#M57012</link>
      <description>Which operating system?  Under the NT family you have Dr. Watson dumps and mini dumps.&lt;BR /&gt;&lt;BR /&gt;James</description>
      <pubDate>Sat, 19 Oct 2002 00:00:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839019#M57012</guid>
      <dc:creator>james1</dc:creator>
      <dc:date>2002-10-19T00:00:54Z</dc:date>
    </item>
    <item>
      <title>Re: Core file equivalent on Windows</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839020#M57013</link>
      <description>Good thought, but I'm not sure how this would be set up for a distributed application.  In other words, can you do this if the program is started by a service on a remote host that is not known to the user at launch time?&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Sat, 19 Oct 2002 01:52:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839020#M57013</guid>
      <dc:creator>bradlepc</dc:creator>
      <dc:date>2002-10-19T01:52:33Z</dc:date>
    </item>
    <item>
      <title>Re: Core file equivalent on Windows</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839021#M57014</link>
      <description>By the way, this is W2K pro.&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Sat, 19 Oct 2002 01:56:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839021#M57014</guid>
      <dc:creator>bradlepc</dc:creator>
      <dc:date>2002-10-19T01:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: Core file equivalent on Windows</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839022#M57015</link>
      <description>You might try something like calling MiniDumpWriteDump from an exception handler, that should work for any case.  For W2K you would need to distribute DbgHelp.dll to have access to this function.  See &lt;A href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/minidump_files.asp"&gt;the docs for minidumps&lt;/A&gt;.&lt;BR /&gt;&lt;BR /&gt;James</description>
      <pubDate>Mon, 21 Oct 2002 12:26:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Core-file-equivalent-on-Windows/m-p/839022#M57015</guid>
      <dc:creator>james1</dc:creator>
      <dc:date>2002-10-21T12:26:19Z</dc:date>
    </item>
  </channel>
</rss>

