- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Refers to: Intel Compiler Suite 11.0-069 @ LINUX x86_64, Rocksclusters Linux 4.3 (Mars Hill)
First bug - in release 11.0 there is no longer a shell script in order to set (or source) the idb environment correctly. Try this:
[P000002D@faraday ~]$ which iidb
/opt/intel/Compiler/11.0/069/bin/intel64/iidb
[P000002D@faraday ~]$ ldd /opt/intel/Compiler/11.0/069/bin/intel64/iidb
libc.so.6 => /lib64/tls/libc.so.6 (0x0000003532e00000)
libPostOffice.so => not found
libxerces-c.so.27 => not found
libDebuggerData.so => not found
libDebuggerServices.so => not found
libScheduler.so => not found
libdl.so.2 => /lib64/libdl.so.2 (0x0000003533300000)
libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x0000003533700000)
libm.so.6 => /lib64/tls/libm.so.6 (0x0000003533100000)
libstdc++.so.5 => /usr/lib64/libstdc++.so.5 (0x0000002a9557b000)
/lib64/ld-linux-x86-64.so.2 (0x0000003531e00000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003535100000)
[P000002D@faraday ~]$
Now set in .bashrc:
export LD_LIBRARY_PATH=/opt/intel/Compiler/11.0/069/idb/lib/intel64:$LD_LIBRARY_PATH
Then iidb shows no more missing libraries:
[P000002D@faraday ~]$ ldd /opt/intel/Compiler/11.0/069/bin/intel64/iidb
libc.so.6 => /lib64/tls/libc.so.6 (0x0000003532e00000)
libPostOffice.so => /opt/intel/Compiler/11.0/069/idb/lib/intel64/libPostOffice.so (0x0000002a95579000)
libxerces-c.so.27 => /opt/intel/Compiler/11.0/069/idb/lib/intel64/libxerces-c.so.27 (0x0000002a9568c000)
libDebuggerData.so => /opt/intel/Compiler/11.0/069/idb/lib/intel64/libDebuggerData.so (0x0000002a95b87000)
libDebuggerServices.so => /opt/intel/Compiler/11.0/069/idb/lib/intel64/libDebuggerServices.so (0x0000002a95e21000)
libScheduler.so => /opt/intel/Compiler/11.0/069/idb/lib/intel64/libScheduler.so (0x0000002a96055000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003533300000)
libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x0000003533700000)
libm.so.6 => /lib64/tls/libm.so.6 (0x0000003533100000)
libstdc++.so.5 => /usr/lib64/libstdc++.so.5 (0x0000002a96159000)
/lib64/ld-linux-x86-64.so.2 (0x0000003531e00000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003535100000)
[P000002D@faraday ~]$
So far I had no problems with this, but I always feel a little bit uncomfortable when dynmic libs are nor resolved...
Second bug:
I tried to debug a threaded programm using the new exciting idb GUI - so I made a binary (called here ba) with all the usual debug info included and with OpenMP support. Interestingly the following happens, for the sake of simplicity shown here using the CLI-driven idbc:
[P000002D@faraday trunk]$ idbc ba
Intel Debugger for applications running on Intel 64, Version 11.0, Build [1.1510.2.66]
------------------
object file name: ba
Reading symbols from /home/P000002D/sw/beams/trunk/ba...done.
Can't load libomp_db library. OpenMP support is disabled.
$threadlevel is set to "native".
(idb) q
[P000002D@faraday trunk]$
So debugging is possible - but without OpenMP-support. I figured out that this is an architecture problem in the relevant library libomp_db.so:
[P000002D@faraday intel64]$ pwd
/opt/intel/Compiler/11.0/069/lib/intel64
[P000002D@faraday intel64]$ file libomp_db.so
libomp_db.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
[P000002D@faraday intel64]$
There is no other 32-bit lib in that directory and I have only installed the intel64 components of the Intel Compiler Suite 11.0. I suppose - though I am not sure - that this is the cause of the idb-openmp problem.
I think I'm going to open an issue for this.
Regards,
Michael
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
The one ifortvars script sets environments for everything which comes with the 11.0 compiler. I, for one, like this feature.
I second your findings about the OpenMP debug library. I don't know if that is the full extent of the problem, but please do file a report.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
DearMichael,
bug 1) - If you look in your installation at the directory
/opt/intel/Compiler/11.0/69/bin/intel64,
you should hopefully find the familiar idbvars.sh environment configuration script.At least I do on my installation. This is a slightly different location than for the compiler configuration scripts which may be a bit confusing. Regardless of this with your export command for LD_LIBRARY_PATH in ./bashrc you are doing exactly the right thingand thus you should not run into any problems.
bug 2) - This lib-openmp issue looks like an installation packaging problem, that probably needs to be escalated. Did you go ahead and file the issue in Intel Premier Support as you intended to do?
Thanks, Rob
