IDB debugging of a 32 bit MPI app on Intel Cluster Dev Toolkit 11.1

IDB debugging of a 32 bit MPI app on Intel Cluster Dev Toolkit 11.1

I am having issues debugging a 32 bit C++/ MPI app on a Red Hat 5.4 Enterprise 64 bit/ Intel 5500 Xeon system, Intel Cluster Development Toolkit, Compiler Ed. 11.1, Python 2.4.3

I have followed another post that said to change idb to link to the command line version idbc.

My tools are as follows:

which idb -> /opt/intel/Compiler/11.1/072/bin/intel64/idb
which mpiexec -> /opt/intel/impi/4.0.0.028/ia32/bin/mpiexec
which mpiicc -> /opt/intel/impi/4.0.0.028/ia32/bin/mpiicc
which mpdboot -> /opt/intel/impi/4.0.0.028/ia32/bin/mpdboot

$ mpiicc -g mpi_testsome.cpp -o mpi_testsome
$mpdboot -n 1
$mpiexec -idb -n 10 -env I_MPI_FAULT_CONTINUE on -env I_MPI_FABRICS tcp:tcp ./mpi_testsome

mpd_uncaught_exception_tb handling:
exceptions.ImportError: /opt/intel/impi/4.0.0.028/ia32/bin/mtv.so: wrong ELFCLASS32
/opt/intel/impi/4.0.0.028/ia32/bin/mpiexec 1196 mpiexec import mtv
/opt/intel/impi/4.0.0.028/ia32/bin/mpiexec 3205 ? mpiexec()

All of my files seem to be 32 bit binaries. Any ideas on what is wrong?

3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi Jim,

Might be "file `which python`" will help you to understand the reason?
You are using 64-bit python which is trying to 'import' 32-bit mtv.so library, hence the error.

Everything in your enviroment has to be 32-bit.

Regards!
Dmitry

After some playing with the 32 bit python package, I got it working by having a /usr/bin/python32 in addition to the /usr/bin/python which was 64 bit. I modified /ia32/mpiexec to call python32 and all works now. Thanks for the insight.

Leave a Comment

Please sign in to add a comment. Not a member? Join today