<?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: Intel Fortran debugger and MPICH in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898648#M2158</link>
    <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/423452"&gt;Dmitry Kuzmin (Intel)&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;
&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;BR /&gt;Hi Thomas,&lt;BR /&gt;&lt;BR /&gt;Thank you for the interest to Intel products.&lt;BR /&gt;&lt;BR /&gt;The command line looks very strange. It should look like:&lt;BR /&gt;"xterm -e idb -pid &lt;PID_OF_MPIEXEC&gt; -mpi2 -parallel /usr/bin/python"&lt;BR /&gt;&lt;BR /&gt;Also you should set environment variables:&lt;BR /&gt;IDB_HOME=&lt;WHERE_IDB_IS_LOCATED&gt;&lt;BR /&gt;LD_LIBRARY_PATH=&lt;WHERE_IDB_LIBRARIES_ARE_LOCATED&gt;&lt;BR /&gt;IDB_PARALLEL_SHELL=&lt;FULL_PATH_TO_SSH&gt; - you don't need this var if you use rsh connection.&lt;BR /&gt;Probably, MPIEXEC_DEBUG=1&lt;BR /&gt;&lt;BR /&gt;I hope this helps.&lt;BR /&gt;&lt;BR /&gt;Best wishes,&lt;BR /&gt; Dmitry&lt;BR /&gt;&lt;BR /&gt;&lt;/FULL_PATH_TO_SSH&gt;&lt;/WHERE_IDB_LIBRARIES_ARE_LOCATED&gt;&lt;/WHERE_IDB_IS_LOCATED&gt;&lt;/PID_OF_MPIEXEC&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
Hi Dmitry,&lt;BR /&gt;I finally got to trying that out, but setting the IDB_PARALLEL_SHELL and MPIEXEC_DEBUG as you said made things hang. When I have only IDB_HOME and LD_LIBRARY_PATH set, I can somehow start the debugger and it seems to try to attach somehow to the process (although I don't understand why the last argument is the python executable and not the actual program executable), but then it says:&lt;BR /&gt;Intel Debugger for applications running on IA-32, Version 9.1-28, Build 20070305&lt;BR /&gt;Reading symbolic information from /opt/rocks/bin/python2.4...No debugging symbols found&lt;BR /&gt;Attached to process id 27609 ....&lt;BR /&gt;stopped at [&lt;OPAQUE&gt; _dl_sysinfo_int80(...) 0x008ca7a2] &lt;BR /&gt;Symbol "MPIR_being_debugged" is not defined.&lt;BR /&gt;Symbol "MPIR_Breakpoint" is not defined.&lt;BR /&gt;Symbol "MPIR_Breakpoint" is not defined.&lt;BR /&gt;::MPIR_Breakpoint has no valid breakpoint address&lt;BR /&gt;Make breakpoint pending on future shared library load? (y or &lt;N&gt;) &lt;BR /&gt;Warning: Breakpoint not set&lt;BR /&gt;&lt;BR /&gt;and hangs, no matter whether I have chosen y or n in the breakpoint question.&lt;BR /&gt;&lt;BR /&gt;So, as that failed, I was prompted to look back into my MPICH installation again and notice that for some reason, it says in the configure log:&lt;BR /&gt;configure: WARNING: unrecognized options: --enable-debuginfo&lt;BR /&gt;&lt;BR /&gt;although according to the installation guide, this is the option I should give to "provide access to the message queues for debuggers". In the configure log, it also says later:&lt;BR /&gt;checking debugging support... no&lt;BR /&gt;although I'm not sure whether that refers to this kind of debugging or rather to the debugging options for MPICH2 developpers themselves (which would not be of interest for me).&lt;BR /&gt;So basically, I'm rather confused about the error messages and wonder if I have to build MPICH2 in a different way to make the Intel debugger work (and if so, how).&lt;BR /&gt;May the problem lie here already, and how do you build MPICH2 then?&lt;BR /&gt;Thomas&lt;BR /&gt;&lt;/N&gt;&lt;/OPAQUE&gt;</description>
    <pubDate>Fri, 30 Oct 2009 22:45:45 GMT</pubDate>
    <dc:creator>truedas</dc:creator>
    <dc:date>2009-10-30T22:45:45Z</dc:date>
    <item>
      <title>Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898644#M2154</link>
      <description>Hi,&lt;BR /&gt;I want to debug this parallel Fortran program that I'm trying to make run on a Linux-type cluster using the Intel Fortran compiler (v.9.1.045) and debugger (v.9.1-28) and MPICH2.1.2. While building the executable with the -g option is straightforward, but when trying to invoke the compiler it crashes with this message:&lt;BR /&gt;$ idb -parallel mpiexec -machinefile machines -n 4 ./stagyympi &lt;BR /&gt;Intel Debugger for applications running on IA-32, Version 9.1-28, Build 20070305&lt;BR /&gt;execve failed: No such file or directory&lt;BR /&gt;Error: could not start debuggee&lt;BR /&gt;Could not start process for mpiexec&lt;BR /&gt;No image loaded ... Recovering ... &lt;BR /&gt;&lt;BR /&gt;Any ideas what may be wrong here?&lt;BR /&gt;Thomas</description>
      <pubDate>Thu, 29 Oct 2009 19:47:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898644#M2154</guid>
      <dc:creator>truedas</dc:creator>
      <dc:date>2009-10-29T19:47:49Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898645#M2155</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
There was a thread several years ago about idb (now named idbc) and mpich:&lt;BR /&gt;&lt;A href="http://software.intel.com/en-us/forums/showthread.php?t=50526"&gt;http://software.intel.com/en-us/forums/showthread.php?t=50526&lt;/A&gt;&lt;BR /&gt;Is there nothing about updates to this on the mpich2 support sites? Did it change that much?&lt;BR /&gt;Your command line appears to invoke debugging of mpiexec, not of your program.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Oct 2009 22:48:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898645#M2155</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2009-10-29T22:48:50Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898646#M2156</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/367365"&gt;tim18&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt; There was a thread several years ago about idb (now named idbc) and mpich:&lt;BR /&gt;&lt;A href="http://software.intel.com/en-us/forums/showthread.php?t=50526"&gt;http://software.intel.com/en-us/forums/showthread.php?t=50526&lt;/A&gt;&lt;BR /&gt;Is there nothing about updates to this on the mpich2 support sites? Did it change that much?&lt;BR /&gt;Your command line appears to invoke debugging of mpiexec, not of your program.&lt;BR /&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
I guess there have been some changes. I have tried out what was suggested in that thread and it didn't work either:&lt;BR /&gt;neither mpirun nor the now recommended mpiexec recognize -dbg=idb as a valid option, whereas invoking it as&lt;BR /&gt;mpiexec -machinefile machines -n 1 idb stagyympi &lt;BR /&gt;yields:&lt;BR /&gt;problem with execution of idb on compute-0-0.local: [Errno 2] No such file or directory &lt;BR /&gt;So, no luck there. Any other ideas?&lt;BR /&gt;Thomas&lt;BR /&gt;</description>
      <pubDate>Fri, 30 Oct 2009 03:08:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898646#M2156</guid>
      <dc:creator>truedas</dc:creator>
      <dc:date>2009-10-30T03:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898647#M2157</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/449851"&gt;truedas&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;$ idb -parallel mpiexec -machinefile machines -n 4 ./stagyympi &lt;BR /&gt;&lt;BR /&gt;Any ideas what may be wrong here?&lt;BR /&gt;Thomas&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;Hi Thomas,&lt;BR /&gt;&lt;BR /&gt;Thank you for the interest to Intel products.&lt;BR /&gt;&lt;BR /&gt;The command line looks very strange. It should look like:&lt;BR /&gt;"xterm -e idb -pid &lt;PID_OF_MPIEXEC&gt; -mpi2 -parallel /usr/bin/python"&lt;BR /&gt;&lt;BR /&gt;Also you should set environment variables:&lt;BR /&gt;IDB_HOME=&lt;WHERE_IDB_IS_LOCATED&gt;&lt;BR /&gt;LD_LIBRARY_PATH=&lt;WHERE_IDB_LIBRARIES_ARE_LOCATED&gt;&lt;BR /&gt;IDB_PARALLEL_SHELL=&lt;FULL_PATH_TO_SSH&gt; - you don't need this var if you use rsh connection.&lt;BR /&gt;Probably, MPIEXEC_DEBUG=1&lt;BR /&gt;&lt;BR /&gt;I hope this helps.&lt;BR /&gt;&lt;BR /&gt;Best wishes,&lt;BR /&gt; Dmitry&lt;BR /&gt;&lt;BR /&gt;&lt;/FULL_PATH_TO_SSH&gt;&lt;/WHERE_IDB_LIBRARIES_ARE_LOCATED&gt;&lt;/WHERE_IDB_IS_LOCATED&gt;&lt;/PID_OF_MPIEXEC&gt;</description>
      <pubDate>Fri, 30 Oct 2009 05:57:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898647#M2157</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2009-10-30T05:57:50Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898648#M2158</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/423452"&gt;Dmitry Kuzmin (Intel)&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;
&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;BR /&gt;Hi Thomas,&lt;BR /&gt;&lt;BR /&gt;Thank you for the interest to Intel products.&lt;BR /&gt;&lt;BR /&gt;The command line looks very strange. It should look like:&lt;BR /&gt;"xterm -e idb -pid &lt;PID_OF_MPIEXEC&gt; -mpi2 -parallel /usr/bin/python"&lt;BR /&gt;&lt;BR /&gt;Also you should set environment variables:&lt;BR /&gt;IDB_HOME=&lt;WHERE_IDB_IS_LOCATED&gt;&lt;BR /&gt;LD_LIBRARY_PATH=&lt;WHERE_IDB_LIBRARIES_ARE_LOCATED&gt;&lt;BR /&gt;IDB_PARALLEL_SHELL=&lt;FULL_PATH_TO_SSH&gt; - you don't need this var if you use rsh connection.&lt;BR /&gt;Probably, MPIEXEC_DEBUG=1&lt;BR /&gt;&lt;BR /&gt;I hope this helps.&lt;BR /&gt;&lt;BR /&gt;Best wishes,&lt;BR /&gt; Dmitry&lt;BR /&gt;&lt;BR /&gt;&lt;/FULL_PATH_TO_SSH&gt;&lt;/WHERE_IDB_LIBRARIES_ARE_LOCATED&gt;&lt;/WHERE_IDB_IS_LOCATED&gt;&lt;/PID_OF_MPIEXEC&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
Hi Dmitry,&lt;BR /&gt;I finally got to trying that out, but setting the IDB_PARALLEL_SHELL and MPIEXEC_DEBUG as you said made things hang. When I have only IDB_HOME and LD_LIBRARY_PATH set, I can somehow start the debugger and it seems to try to attach somehow to the process (although I don't understand why the last argument is the python executable and not the actual program executable), but then it says:&lt;BR /&gt;Intel Debugger for applications running on IA-32, Version 9.1-28, Build 20070305&lt;BR /&gt;Reading symbolic information from /opt/rocks/bin/python2.4...No debugging symbols found&lt;BR /&gt;Attached to process id 27609 ....&lt;BR /&gt;stopped at [&lt;OPAQUE&gt; _dl_sysinfo_int80(...) 0x008ca7a2] &lt;BR /&gt;Symbol "MPIR_being_debugged" is not defined.&lt;BR /&gt;Symbol "MPIR_Breakpoint" is not defined.&lt;BR /&gt;Symbol "MPIR_Breakpoint" is not defined.&lt;BR /&gt;::MPIR_Breakpoint has no valid breakpoint address&lt;BR /&gt;Make breakpoint pending on future shared library load? (y or &lt;N&gt;) &lt;BR /&gt;Warning: Breakpoint not set&lt;BR /&gt;&lt;BR /&gt;and hangs, no matter whether I have chosen y or n in the breakpoint question.&lt;BR /&gt;&lt;BR /&gt;So, as that failed, I was prompted to look back into my MPICH installation again and notice that for some reason, it says in the configure log:&lt;BR /&gt;configure: WARNING: unrecognized options: --enable-debuginfo&lt;BR /&gt;&lt;BR /&gt;although according to the installation guide, this is the option I should give to "provide access to the message queues for debuggers". In the configure log, it also says later:&lt;BR /&gt;checking debugging support... no&lt;BR /&gt;although I'm not sure whether that refers to this kind of debugging or rather to the debugging options for MPICH2 developpers themselves (which would not be of interest for me).&lt;BR /&gt;So basically, I'm rather confused about the error messages and wonder if I have to build MPICH2 in a different way to make the Intel debugger work (and if so, how).&lt;BR /&gt;May the problem lie here already, and how do you build MPICH2 then?&lt;BR /&gt;Thomas&lt;BR /&gt;&lt;/N&gt;&lt;/OPAQUE&gt;</description>
      <pubDate>Fri, 30 Oct 2009 22:45:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898648#M2158</guid>
      <dc:creator>truedas</dc:creator>
      <dc:date>2009-10-30T22:45:45Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898649#M2159</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/449851"&gt;truedas&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;
&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
Hi Dmitry,&lt;BR /&gt;I finally got to trying that out, but setting the IDB_PARALLEL_SHELL and MPIEXEC_DEBUG as you said made things hang. When I have only IDB_HOME and LD_LIBRARY_PATH set, I can somehow start the debugger and it seems to try to attach somehow to the process (although I don't understand why the last argument is the python executable and not the actual program executable), but then it says:&lt;BR /&gt;Intel Debugger for applications running on IA-32, Version 9.1-28, Build 20070305&lt;BR /&gt;Reading symbolic information from /opt/rocks/bin/python2.4...No debugging symbols found&lt;BR /&gt;Attached to process id 27609 ....&lt;BR /&gt;stopped at [&lt;OPAQUE&gt; _dl_sysinfo_int80(...) 0x008ca7a2] &lt;BR /&gt;Symbol "MPIR_being_debugged" is not defined.&lt;BR /&gt;Symbol "MPIR_Breakpoint" is not defined.&lt;BR /&gt;Symbol "MPIR_Breakpoint" is not defined.&lt;BR /&gt;::MPIR_Breakpoint has no valid breakpoint address&lt;BR /&gt;Make breakpoint pending on future shared library load? (y or &lt;N&gt;) &lt;BR /&gt;Warning: Breakpoint not set&lt;BR /&gt;&lt;BR /&gt;and hangs, no matter whether I have chosen y or n in the breakpoint question.&lt;BR /&gt;&lt;BR /&gt;So, as that failed, I was prompted to look back into my MPICH installation again and notice that for some reason, it says in the configure log:&lt;BR /&gt;configure: WARNING: unrecognized options: --enable-debuginfo&lt;BR /&gt;&lt;BR /&gt;although according to the installation guide, this is the option I should give to "provide access to the message queues for debuggers". In the configure log, it also says later:&lt;BR /&gt;checking debugging support... no&lt;BR /&gt;although I'm not sure whether that refers to this kind of debugging or rather to the debugging options for MPICH2 developpers themselves (which would not be of interest for me).&lt;BR /&gt;So basically, I'm rather confused about the error messages and wonder if I have to build MPICH2 in a different way to make the Intel debugger work (and if so, how).&lt;BR /&gt;May the problem lie here already, and how do you build MPICH2 then?&lt;BR /&gt;Thomas&lt;BR /&gt;&lt;/N&gt;&lt;/OPAQUE&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;Hi Thomas,&lt;BR /&gt;&lt;BR /&gt;I was talking about Intel MPI Library and IDB.&lt;BR /&gt;I don't know how MPICH supports IDB, but invocation looked incorrectly. Probably MPICH was configured incorrecly during installation.&lt;BR /&gt;An application hangs because of MPIEXEC_DEBUG variable.&lt;BR /&gt;&lt;BR /&gt;IDB attaches to a python script first to get information about running processes from mtv.so. Mpiexec should wait for a debugger.&lt;BR /&gt;&lt;BR /&gt;BTW: your IDB is very old... March 2007 - I'm not sure that IDB could work correctly with MPI-2 applications at that time. Could you get idb 10.1 somehow?&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Nov 2009 07:04:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898649#M2159</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2009-11-02T07:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898650#M2160</link>
      <description>Some clarifications about idb 9.1 usage with mpich:&lt;BR /&gt;&lt;BR /&gt;The correct start up command is:&lt;BR /&gt;mpirun -dbg=idb -np &lt;NUMBER of="" processes=""&gt; &lt;BINARY name=""&gt;&lt;BR /&gt;&lt;BR /&gt;Two pre-requisites:&lt;BR /&gt;1. The environment variable IDB_HOME needs to be set to the directory where IDB resides.&lt;BR /&gt;2. The file mpirun_dbg.idb, which is included in the IDB 9.1 distribution, needs to be put in the "bin" directory of the MPICH installation.&lt;BR /&gt;&lt;BR /&gt;Please try this out and let me know if this helps.&lt;BR /&gt;&lt;BR /&gt;Best wishes,&lt;BR /&gt; Dmitry&lt;BR /&gt;&lt;BR /&gt;&lt;/BINARY&gt;&lt;/NUMBER&gt;</description>
      <pubDate>Tue, 03 Nov 2009 06:03:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898650#M2160</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2009-11-03T06:03:55Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898651#M2161</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/423452"&gt;Dmitry Kuzmin (Intel)&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;Some clarifications about idb 9.1 usage with mpich:&lt;BR /&gt;&lt;BR /&gt;The correct start up command is:&lt;BR /&gt;mpirun -dbg=idb -np &lt;NUMBER of="" processes=""&gt; &lt;BINARY name=""&gt;&lt;BR /&gt;&lt;BR /&gt;Two pre-requisites:&lt;BR /&gt;1. The environment variable IDB_HOME needs to be set to the directory where IDB resides.&lt;BR /&gt;2. The file mpirun_dbg.idb, which is included in the IDB 9.1 distribution, needs to be put in the "bin" directory of the MPICH installation.&lt;BR /&gt;&lt;BR /&gt;Please try this out and let me know if this helps.&lt;BR /&gt;&lt;BR /&gt;Best wishes,&lt;BR /&gt; Dmitry&lt;BR /&gt;&lt;BR /&gt;&lt;/BINARY&gt;&lt;/NUMBER&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
Hi Dmitry,&lt;BR /&gt;thanks for the info, and sorry for being slow with the response.&lt;BR /&gt;&lt;BR /&gt;I guess it will be difficult to get my hands on a more recent version of the compiler on that architecture, but I tried it now with the version, and it still doesn't work.&lt;BR /&gt;$ echo $IDB_HOME&lt;BR /&gt; /opt/intel/idb/9.1.045/&lt;BR /&gt;I also copied mpirun_dbg.idb into the bin directory where the MPICH executables live, but neither mpirun nor mpiexec recognize the option -gdb:&lt;BR /&gt;$ mpirun -gdb=idb -np 4 stagyympi&lt;BR /&gt; invalid "local" arg: -gdb=idb&lt;BR /&gt;&lt;BR /&gt;I have looked in the installation guide if there is a way to "teach" MPICH the use of compilers other than gdb, but have found none.&lt;BR /&gt;&lt;BR /&gt;Thomas&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Nov 2009 05:54:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898651#M2161</guid>
      <dc:creator>truedas</dc:creator>
      <dc:date>2009-11-06T05:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Fortran debugger and MPICH</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898652#M2162</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/449851"&gt;truedas&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;
&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
I have looked in the installation guide if there is a way to "teach" MPICH the use of compilers other than gdb, but have found none.&lt;BR /&gt;&lt;BR /&gt;Thomas&lt;BR /&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;I've looked into the MPICH2 mpiexec.py script and seems they support only GDB (-gdb) and TV (-tv) debuggers. -gdb option doesn't have parameters.&lt;BR /&gt;Unfortunately it's not so easy to modify mpiexec.py so that it would work with idb. If you wanna use IDB you probably need to install Intel MPI Library.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Nov 2009 14:42:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Intel-Fortran-debugger-and-MPICH/m-p/898652#M2162</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2009-11-06T14:42:11Z</dc:date>
    </item>
  </channel>
</rss>

