<?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 Hi Jack,  in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/A-Bus-error/m-p/1081205#M4890</link>
    <description>&lt;P&gt;Hi Jack,&amp;nbsp;&lt;/P&gt;

&lt;P&gt;If you have also the Intel tools ITAC (Intel Trace Analyzer and collector) and Inspector XE available (part of the Cluster Studio) you may try the following analyis:&lt;/P&gt;

&lt;P&gt;1. initialize ITAC . Code may be compiled with -g for better results showing line numbers etc.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;2. run your code with an additional flag (-check_mpi):&lt;/P&gt;

&lt;P&gt;$ mpirun -check_mpi -n &amp;lt;N&amp;gt; ./prg.x&lt;/P&gt;

&lt;P&gt;errors and warnings will be printed on stdout. This will just analyze the MPI usage.&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;For memory and threading bugs you may use Intel Inspector.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;1. &amp;nbsp;initialize Inspector &amp;nbsp;. code should be compiled with -g&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;2. Run an analyis on the rank that is causing trouble e.g. 13. This can be done in a convenient way by using the "-gtool" flag or the I_MPI_GTOOL variable.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;export I_MPI_GTOOL="inspxe-cl&amp;nbsp;--collect mi1 --result-dir mi1 :13"&lt;/P&gt;

&lt;P&gt;run your code in the normal way.&amp;nbsp;&lt;BR /&gt;
	Please have a look at the Inspector documentation. You may simply try "inspxe-cl -h" for a start. The analysis above is just looking for mem leaks. More involved analysis can run for a long time. Please limit to a few time steps.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;best regards,&lt;BR /&gt;
	Heinrich&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 14 Apr 2016 08:03:42 GMT</pubDate>
    <dc:creator>Heinrich_B_Intel</dc:creator>
    <dc:date>2016-04-14T08:03:42Z</dc:date>
    <item>
      <title>A Bus error</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/A-Bus-error/m-p/1081204#M4889</link>
      <description>&lt;DIV class="forum-post-content"&gt;
	&lt;DIV class="field field-name-body field-type-text-with-summary field-label-hidden"&gt;
		&lt;DIV class="field-items"&gt;
			&lt;DIV class="field-item even"&gt;
				&lt;P&gt;Hi all,&lt;/P&gt;

				&lt;P&gt;I'm running a pretty heavy MPI application (the WRF model) on Linux and get a BUS error (please see below the output for the type of the error) --- any idea how to isolate the cause (specific line of bad coding), or system/compiler/MPI related issue ?&lt;/P&gt;

				&lt;P&gt;Have you guys had an experience of catching these bugs with one of Intel's new tools ?&lt;/P&gt;

				&lt;P&gt;Thanks in advance for your perspective and experience,&lt;/P&gt;

				&lt;P&gt;Jack.&lt;/P&gt;

				&lt;P&gt;###&lt;/P&gt;

				&lt;P&gt;rsl.error.0010:[n13:mpi_rank_10][error_sighandler] Caught error: Bus error (signal 7)&lt;/P&gt;
			&lt;/DIV&gt;
		&lt;/DIV&gt;
	&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 08 Apr 2016 15:54:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/A-Bus-error/m-p/1081204#M4889</guid>
      <dc:creator>Jack_S_</dc:creator>
      <dc:date>2016-04-08T15:54:09Z</dc:date>
    </item>
    <item>
      <title>Hi Jack, </title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/A-Bus-error/m-p/1081205#M4890</link>
      <description>&lt;P&gt;Hi Jack,&amp;nbsp;&lt;/P&gt;

&lt;P&gt;If you have also the Intel tools ITAC (Intel Trace Analyzer and collector) and Inspector XE available (part of the Cluster Studio) you may try the following analyis:&lt;/P&gt;

&lt;P&gt;1. initialize ITAC . Code may be compiled with -g for better results showing line numbers etc.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;2. run your code with an additional flag (-check_mpi):&lt;/P&gt;

&lt;P&gt;$ mpirun -check_mpi -n &amp;lt;N&amp;gt; ./prg.x&lt;/P&gt;

&lt;P&gt;errors and warnings will be printed on stdout. This will just analyze the MPI usage.&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;For memory and threading bugs you may use Intel Inspector.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;1. &amp;nbsp;initialize Inspector &amp;nbsp;. code should be compiled with -g&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;2. Run an analyis on the rank that is causing trouble e.g. 13. This can be done in a convenient way by using the "-gtool" flag or the I_MPI_GTOOL variable.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;export I_MPI_GTOOL="inspxe-cl&amp;nbsp;--collect mi1 --result-dir mi1 :13"&lt;/P&gt;

&lt;P&gt;run your code in the normal way.&amp;nbsp;&lt;BR /&gt;
	Please have a look at the Inspector documentation. You may simply try "inspxe-cl -h" for a start. The analysis above is just looking for mem leaks. More involved analysis can run for a long time. Please limit to a few time steps.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;best regards,&lt;BR /&gt;
	Heinrich&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2016 08:03:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/A-Bus-error/m-p/1081205#M4890</guid>
      <dc:creator>Heinrich_B_Intel</dc:creator>
      <dc:date>2016-04-14T08:03:42Z</dc:date>
    </item>
  </channel>
</rss>

