<?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 Problem using the Intel Debugger with Intel MPI Library in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768648#M119</link>
    <description>The issue with Py_InitModule4 has been fixed in Intel MPI Library version 4.0.1&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry</description>
    <pubDate>Wed, 18 Aug 2010 12:19:17 GMT</pubDate>
    <dc:creator>Dmitry_K_Intel2</dc:creator>
    <dc:date>2010-08-18T12:19:17Z</dc:date>
    <item>
      <title>Problem using the Intel Debugger with Intel MPI Library</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768642#M113</link>
      <description>&lt;SPAN class="sectionbody"&gt;Hi,&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

I am trying to debug a code (vat_3d_59_debug) using the Intel Debugger with the Intel MPI Library using the following command:&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

mpiexec -idb -genv MPIEXEC_DEBUG 2 -n 2 -host dragon ./vat_3d_59_debug&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

and I got the following error message:&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

mpiexec_dragon: mpd_uncaught_except_tb handling:&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
  &lt;/SPAN&gt;&lt;TYPE&gt;&lt;SPAN class="sectionbody"&gt;(type 'exceptions.ImportError'): /opt/intel/impi/4.0.0.028/intel64/bin/mtv.so: undefined symbol: Py_InitModule4&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
    /opt/intel/impi/4.0.0.028/bin64/mpiexec  1196  mpiexec&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
        import mtv&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
    /opt/intel/impi/4.0.0.028/bin64/mpiexec  3205  &lt;/SPAN&gt;&lt;MODULE&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
        mpiexec()&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

The environmental variables associated to the Intel Cluster Toolkit Compiler Edition are set in the .bash_profile as:&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

export INTEL_LICENSE_FILE=/opt/intel/licenses&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
. /opt/intel/ictce/4.0.0.020/ictvars.sh&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
. /opt/intel/Compiler/11.1/072/bin/intel64/iccvars_intel64.sh&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
. /opt/intel/Compiler/11.1/072/bin/intel64/ifortvars_intel64.sh&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
. /opt/intel/Compiler/11.1/072/bin/intel64/idbvars.sh&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
export PATH=/opt/intel/impi/4.0.0.028/bin64:${PATH} &lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
export PATH=/usr/lib64/python2.6:${PATH}&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt; 
export LD_LIBRARY_PATH=/opt/intel/Compiler/11.1/072/lib/intel64:${LD_LIBRARY_PATH}&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
export I_MPI_FABRICS=shm&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
export PATH=/home/roboto/multi_purpose_daemon:${PATH}&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt; 
export JRE=/usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
export PATH=${PATH}:${JRE}/bin&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
. /opt/intel/Compiler/11.1/072/bin/iccvars.sh intel64&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
export IDB_HOME=/opt/intel/Compiler/11.1/072/bin/intel64&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;
export LD_LIBRARY_PATH=/opt/intel/Compiler/11.1/072/idb/lib/intel64:${LD_LIBRARY_PATH}&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

It is worth to mention that the same code runs with no problems using mpiexec when the Intel Debugger is not invoked using:&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

mpiexec -n 2 -host dragon ./vat_3d_59_debug&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

In both cases (with and without the global argument -idb), the mpd was booted using:&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

mpdboot --totalnum=1 --rsh=ssh --ncpus=2&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

Regards,&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class="sectionbody"&gt;

Roboto&lt;/SPAN&gt;&lt;/MODULE&gt;&lt;/TYPE&gt;</description>
      <pubDate>Thu, 05 Aug 2010 00:38:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768642#M113</guid>
      <dc:creator>roboto</dc:creator>
      <dc:date>2010-08-05T00:38:29Z</dc:date>
    </item>
    <item>
      <title>Problem using the Intel Debugger with Intel MPI Library</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768643#M114</link>
      <description>&lt;P&gt;Hi Roboto,&lt;/P&gt;&lt;P&gt;Most likely, what you're experiencing is a known issue when running with the Intel Debugger under the Intel MPI Library daemons. The root cause is pretty simple: by default, IDB starts up in GUI-mode on Linux. You just need to make sure you use the command line interface instead. &lt;A href="http://software.intel.com/en-us/articles/mpiexec-idb-fails-to-start-the-intel-gui-debugger-correctly/"&gt;The following article&lt;/A&gt; describes the issue in more detail and provides a workaround.&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;~Gergana&lt;/P&gt;</description>
      <pubDate>Thu, 05 Aug 2010 21:51:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768643#M114</guid>
      <dc:creator>Gergana_S_Intel</dc:creator>
      <dc:date>2010-08-05T21:51:14Z</dc:date>
    </item>
    <item>
      <title>Problem using the Intel Debugger with Intel MPI Library</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768644#M115</link>
      <description>Hi Gergana,
&lt;BR /&gt;&lt;BR /&gt;
As the article in your post recommended, I did rename idb to idbgui, and then made idb a symbolic link to idbc, the command line IDB. So when I issued the command:&lt;BR /&gt;&lt;BR /&gt;

mpiexec -idb -genv MPIEXEC_DEBUG 1 -n 2 -host dragon ./vat_3d_59_debug&lt;BR /&gt;&lt;BR /&gt;

mpiexec should start running under idbc. But unfortunately, the error message is still the same that I got before:&lt;BR /&gt;&lt;BR /&gt;

mpiexec_dragon: mpd_uncaught_except_tb handling:&lt;BR /&gt;
  &lt;TYPE&gt;: /opt/intel/impi/4.0.0.028/intel64/bin/mtv.so: undefined symbol: Py_InitModule4
    /opt/intel/impi/4.0.0.028/bin64/mpiexec  1196  mpiexec
&lt;BR /&gt;        import mtv
    /opt/intel/impi/4.0.0.028/bin64/mpiexec  3205  &lt;MODULE&gt;
        &lt;BR /&gt;mpiexec()

&lt;BR /&gt;&lt;BR /&gt;I also modified the .bash_profile to include the line:
&lt;BR /&gt;&lt;BR /&gt;
exportIDB_PARALLEL_SHELL=/usr/bin/ssh
&lt;BR /&gt;&lt;BR /&gt;
since the idb documentation stated that by default, the debugger uses rsh to create the leaf debugger
and aggregator processes in the tree structure, but I am still getting the previous error message.
&lt;BR /&gt;&lt;BR /&gt;
Thanks in advance,&lt;BR /&gt;&lt;BR /&gt;

Roboto&lt;/MODULE&gt;&lt;/TYPE&gt;</description>
      <pubDate>Fri, 06 Aug 2010 11:26:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768644#M115</guid>
      <dc:creator>roboto</dc:creator>
      <dc:date>2010-08-06T11:26:21Z</dc:date>
    </item>
    <item>
      <title>Problem using the Intel Debugger with Intel MPI Library</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768645#M116</link>
      <description>Hi Roboto,&lt;BR /&gt;&lt;BR /&gt;Looks like you are using Python 2.5 when we are using 2.4.x.&lt;BR /&gt;Please read &lt;A href="https://launchpad.net/ubuntu/+source/clearsilver/+bug/86685"&gt;this&lt;/A&gt; article - it might help.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Aug 2010 12:37:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768645#M116</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2010-08-06T12:37:39Z</dc:date>
    </item>
    <item>
      <title>Problem using the Intel Debugger with Intel MPI Library</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768646#M117</link>
      <description>Hi Dmitry,&lt;BR /&gt;&lt;BR /&gt;

I am really using Python 2.6. Following your advice, I installed Python 2.4.4 and the problem is gone! I can finally run mpiexec under idb (really idbc opened in a xterm). I want to thank you and Gergana for the very useful and timely thecnical advices.&lt;BR /&gt;&lt;BR /&gt;

Best regards,
&lt;BR /&gt;&lt;BR /&gt;
Roboto</description>
      <pubDate>Fri, 06 Aug 2010 23:30:26 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768646#M117</guid>
      <dc:creator>roboto</dc:creator>
      <dc:date>2010-08-06T23:30:26Z</dc:date>
    </item>
    <item>
      <title>Problem using the Intel Debugger with Intel MPI Library</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768647#M118</link>
      <description>You are welcome, Roboto.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry</description>
      <pubDate>Mon, 09 Aug 2010 06:03:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768647#M118</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2010-08-09T06:03:54Z</dc:date>
    </item>
    <item>
      <title>Problem using the Intel Debugger with Intel MPI Library</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768648#M119</link>
      <description>The issue with Py_InitModule4 has been fixed in Intel MPI Library version 4.0.1&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry</description>
      <pubDate>Wed, 18 Aug 2010 12:19:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Problem-using-the-Intel-Debugger-with-Intel-MPI-Library/m-p/768648#M119</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2010-08-18T12:19:17Z</dc:date>
    </item>
  </channel>
</rss>

