<?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: Two more bugs in idb 11.0 found in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751184#M7560</link>
    <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;P&gt;The 11.0/074 update supplies a 64-bit libomp_dbg.so. One small step forward, I hope.&lt;/P&gt;</description>
    <pubDate>Mon, 24 Nov 2008 22:16:11 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2008-11-24T22:16:11Z</dc:date>
    <item>
      <title>Two more bugs in idb 11.0 found</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751182#M7558</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;SPAN style="text-decoration: underline;"&gt;Refers to: Intel Compiler Suite 11.0-069 @ LINUX x86_64, Rocksclusters Linux 4.3 (Mars Hill)&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;First bug&lt;/STRONG&gt; - in release 11.0 there is no longer a shell script in order to set (or source) the idb environment correctly. Try this:&lt;/P&gt;
&lt;P&gt;[P000002D@faraday ~]$ which iidb&lt;BR /&gt;/opt/intel/Compiler/11.0/069/bin/intel64/iidb&lt;BR /&gt;[P000002D@faraday ~]$ ldd /opt/intel/Compiler/11.0/069/bin/intel64/iidb&lt;BR /&gt; libc.so.6 =&amp;gt; /lib64/tls/libc.so.6 (0x0000003532e00000)&lt;BR /&gt; libPostOffice.so =&amp;gt; not found&lt;BR /&gt; libxerces-c.so.27 =&amp;gt; not found&lt;BR /&gt; libDebuggerData.so =&amp;gt; not found&lt;BR /&gt; libDebuggerServices.so =&amp;gt; not found&lt;BR /&gt; libScheduler.so =&amp;gt; not found&lt;BR /&gt; libdl.so.2 =&amp;gt; /lib64/libdl.so.2 (0x0000003533300000)&lt;BR /&gt; libpthread.so.0 =&amp;gt; /lib64/tls/libpthread.so.0 (0x0000003533700000)&lt;BR /&gt; libm.so.6 =&amp;gt; /lib64/tls/libm.so.6 (0x0000003533100000)&lt;BR /&gt; libstdc++.so.5 =&amp;gt; /usr/lib64/libstdc++.so.5 (0x0000002a9557b000)&lt;BR /&gt; /lib64/ld-linux-x86-64.so.2 (0x0000003531e00000)&lt;BR /&gt; libgcc_s.so.1 =&amp;gt; /lib64/libgcc_s.so.1 (0x0000003535100000)&lt;BR /&gt;[P000002D@faraday ~]$&lt;/P&gt;
&lt;P&gt;Now set in .bashrc:&lt;/P&gt;
&lt;P&gt;export LD_LIBRARY_PATH=/opt/intel/Compiler/11.0/069/idb/lib/intel64:$LD_LIBRARY_PATH&lt;/P&gt;
&lt;P&gt;Then iidb shows no more missing libraries:&lt;/P&gt;
&lt;P&gt;[P000002D@faraday ~]$ ldd /opt/intel/Compiler/11.0/069/bin/intel64/iidb&lt;BR /&gt; libc.so.6 =&amp;gt; /lib64/tls/libc.so.6 (0x0000003532e00000)&lt;BR /&gt; libPostOffice.so =&amp;gt; /opt/intel/Compiler/11.0/069/idb/lib/intel64/libPostOffice.so (0x0000002a95579000)&lt;BR /&gt; libxerces-c.so.27 =&amp;gt; /opt/intel/Compiler/11.0/069/idb/lib/intel64/libxerces-c.so.27 (0x0000002a9568c000)&lt;BR /&gt; libDebuggerData.so =&amp;gt; /opt/intel/Compiler/11.0/069/idb/lib/intel64/libDebuggerData.so (0x0000002a95b87000)&lt;BR /&gt; libDebuggerServices.so =&amp;gt; /opt/intel/Compiler/11.0/069/idb/lib/intel64/libDebuggerServices.so (0x0000002a95e21000)&lt;BR /&gt; libScheduler.so =&amp;gt; /opt/intel/Compiler/11.0/069/idb/lib/intel64/libScheduler.so (0x0000002a96055000)&lt;BR /&gt; libdl.so.2 =&amp;gt; /lib64/libdl.so.2 (0x0000003533300000)&lt;BR /&gt; libpthread.so.0 =&amp;gt; /lib64/tls/libpthread.so.0 (0x0000003533700000)&lt;BR /&gt; libm.so.6 =&amp;gt; /lib64/tls/libm.so.6 (0x0000003533100000)&lt;BR /&gt; libstdc++.so.5 =&amp;gt; /usr/lib64/libstdc++.so.5 (0x0000002a96159000)&lt;BR /&gt; /lib64/ld-linux-x86-64.so.2 (0x0000003531e00000)&lt;BR /&gt; libgcc_s.so.1 =&amp;gt; /lib64/libgcc_s.so.1 (0x0000003535100000)&lt;BR /&gt;[P000002D@faraday ~]$&lt;/P&gt;
&lt;P&gt;So far I had no problems with this, but I always feel a little bit uncomfortable when dynmic libs are nor resolved...&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Second bug:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I tried to debug a threaded programm using the new exciting &lt;EM&gt;idb &lt;/EM&gt;GUI - so I made a binary (called here &lt;EM&gt;ba&lt;/EM&gt;) 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 &lt;EM&gt;idbc&lt;/EM&gt;:&lt;/P&gt;
&lt;P&gt;[P000002D@faraday trunk]$ idbc ba&lt;BR /&gt;Intel Debugger for applications running on Intel 64, Version 11.0, Build [1.1510.2.66]&lt;BR /&gt;------------------&lt;BR /&gt;object file name: ba&lt;BR /&gt;Reading symbols from /home/P000002D/sw/beams/trunk/ba...done.&lt;BR /&gt;Can't load libomp_db library. OpenMP support is disabled.&lt;BR /&gt;$threadlevel is set to "native".&lt;BR /&gt;(idb) q&lt;BR /&gt;[P000002D@faraday trunk]$&lt;/P&gt;
&lt;P&gt;So debugging is possible - but without OpenMP-support. I figured out that this is an architecture problem in the relevant library libomp_db.so:&lt;/P&gt;
&lt;P&gt;[P000002D@faraday intel64]$ pwd&lt;BR /&gt;/opt/intel/Compiler/11.0/069/lib/intel64&lt;BR /&gt;[P000002D@faraday intel64]$ file libomp_db.so&lt;BR /&gt;libomp_db.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped&lt;BR /&gt;[P000002D@faraday intel64]$&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I think I'm going to open an issue for this.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Michael&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Nov 2008 09:14:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751182#M7558</guid>
      <dc:creator>Michael1</dc:creator>
      <dc:date>2008-11-14T09:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: Two more bugs in idb 11.0 found</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751183#M7559</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;P&gt;The one ifortvars script sets environments for everything which comes with the 11.0 compiler. I, for one, like this feature.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Nov 2008 15:26:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751183#M7559</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2008-11-14T15:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: Two more bugs in idb 11.0 found</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751184#M7560</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;P&gt;The 11.0/074 update supplies a 64-bit libomp_dbg.so. One small step forward, I hope.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2008 22:16:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751184#M7560</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2008-11-24T22:16:11Z</dc:date>
    </item>
    <item>
      <title>Re: Two more bugs in idb 11.0 found</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751185#M7561</link>
      <description>&lt;DIV style="margin: 0px; height: auto;"&gt;&lt;/DIV&gt;
&lt;BR /&gt;DearMichael,&lt;BR /&gt;&lt;BR /&gt;bug 1) - If you look in your installation at the directory &lt;BR /&gt;&lt;BR /&gt;/opt/intel/Compiler/11.0/69/bin/intel64,&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;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?&lt;BR /&gt;&lt;BR /&gt;Thanks, Rob</description>
      <pubDate>Wed, 14 Jan 2009 16:42:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751185#M7561</guid>
      <dc:creator>Rob_Mueller-Albrecht</dc:creator>
      <dc:date>2009-01-14T16:42:06Z</dc:date>
    </item>
    <item>
      <title>Re: Two more bugs in idb 11.0 found</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751186#M7562</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
The lib-openmp packaging error was only in 11.0.069, it was caught right away and fixed by the next update, 11.0.074. &lt;BR /&gt;&lt;BR /&gt;ron&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Jan 2009 17:42:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Two-more-bugs-in-idb-11-0-found/m-p/751186#M7562</guid>
      <dc:creator>Ron_Green</dc:creator>
      <dc:date>2009-01-14T17:42:04Z</dc:date>
    </item>
  </channel>
</rss>

