idb won't start

[Matthew_Foster]

I'm not sure if I'm posting in the correct forum, please advise if not.

I can not get idb to start. I'm using version 11.1.073 of the C++ and FORTRAN compilers on RHEL 5.5. When I run idb, I get no feedback at all at the command line. I just get another prompt back. My Java version is 1.6u20. I've tried running the java command from the idb script and get the same result. No errors and no idb.

Any help is appreciated.

Matt

[Ron_Green]

Since idb is a script file, you can run it in debug:

bash -x idb

this will echo each command and this may help.

And X11 forwarding is set up correctly, yes? So you can do:

xclock

for example and you should get a clock display pop up on your X11 desktop?

ron

[Matthew_Foster]

Ron,

Yes, X11 forwarding is working, and I verified that with xclock as you suggested. I have also tried running idb at the console (i.e. NOT through an ssh session) with the same result.

I don't see anything unusual when I run 'bash -x idb', but I'm attaching the output, so you can have a look.

Matt

[Ron_Green]

yes, that output all looks ok. Let's try a few more checks:

ldd /opt/intel/Compiler/11.1/073/bin/intel64/iidb

should look similar to:
libc.so.6 => /lib64/libc.so.6 (0x00000037f9c00000)
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 (0x00000037fa400000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000037fa800000)
libm.so.6 => /lib64/libm.so.6 (0x00000037fa000000)
libstdc++.so.5 => /usr/lib64/libstdc++.so.5 (0x00002aaaaaada000)
/lib64/ld-linux-x86-64.so.2 (0x00000037f9800000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000037fec00000)

The important one: libstdc++.so.5 - make sure this is defined, such as above. What does your ldd show?

ron

[Matthew_Foster]

Ron,

Mine looks very similar to yours...

libc.so.6 => /lib64/libc.so.6 (0x0000003950e00000)
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 (0x0000003951600000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003951a00000)
libm.so.6 => /lib64/libm.so.6 (0x0000003951200000)
libstdc++.so.5 => /usr/lib64/libstdc++.so.5 (0x00002b82c9023000)
/lib64/ld-linux-x86-64.so.2 (0x0000003950a00000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x000000395e800000)

Matt

[Matthew_Foster]

I just updated our compiler suite to Composer XE 2011.3.174 and continue to have the same issue. Additional help would be greatly appreciated.

Matt

[Ron_Green]

Matt,

I notice you have a newer java, 1.6.0_20, correct? and I'm pretty sure that is a JRE from Sun from what I see in your log.

And your OS is RHEL 5.5, correct?

I have an older Java JRE, but I'll go fetch the version you have.

Here's a couple of other tests - ldd on the java executable

rwgreen@spdr65:~> which java
/cts/tools/jre/intel64/jre1.6.0_11/bin/java
rwgreen@spdr65:~> ldd /cts/tools/jre/intel64/jre1.6.0_11/bin/java
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002aef728f2000)
libjli.so => /site/jf/cts2/tools/jre/intel64/jre1.6.0_11/bin/../lib/amd64/jli/libjli.so (0x00002aef72a0b000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002aef72b16000)
libc.so.6 => /lib64/libc.so.6 (0x00002aef72c1a000)
/lib64/ld-linux-x86-64.so.2 (0x00002aef727d6000)
rwgreen@spdr65:~>

And to help isolate this to a java problem and not anything wrong with the idb eclipse launcher jar file, let's run another jar file. there is java jar file that is part of the new 12.0 compiler that used to view the profile output from the new -profile options.

java -jar /opt/intel/composerxe-2011.3.174/bin/loopprofileviewer.jar

see if that runs. I'll go get the _20 JRE and run that on one of my RHEL 5.5 servers.

ron

[Ron_Green]

one other quick note: if you need the debugger immediately, you know you can run the command line version with

idbc

just in case you need a debugger and don't mind command line.

ron

[Ron_Green]

another couple of questions I should have asked:

1) you do 'source /compilervars.sh intel64' with the 12.0 compiler, correct? (looks like you did)

but

2) are you starting idb by itself OR are you passing it a binary?

idb
or
idb a.out

We have seen IDB crash immediately on occassion with odd binaries.

ron

[Matthew_Foster]

[matthew.foster@oun-lw-headnode bin]$ ldd /opt/jdk1.6.0_20/bin/java
linux-gate.so.1 => (0xffffe000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00b7a000)
libjli.so => /opt/jdk1.6.0_20/bin/../jre/lib/i386/jli/libjli.so (0xf7fbb000)
libdl.so.2 => /lib/libdl.so.2 (0x00b68000)
libc.so.6 => /lib/libc.so.6 (0x00a0e000)
/lib/ld-linux.so.2 (0x009ef000)


I executed the other jar file you pointed to, and it came up OK.

Matt

[Matthew_Foster]

Yes. My .bash_profile sources the compiler vars. I've also tried sourcing it manually, just to make sure.

Running idb by itself...no arguments at all.

Also, I have run idbc a bit, and got some useful feedback, but I'm not as comfortable with the CLI version. I'm constantly having to look up the commands. :-\

Matt

[Rob_Mueller-Albrecht]

Dear Matt,

I still wonder whether this may be JRE related, although the version number you provided should be fully compatible. Can you let me know whether you have multiple JREs installed and if so which they are?

Also - it is important that the JRE matches the installation as far as IA32 or Intel64 mode is concerned.
Could you clarify for the OS, the compiler installation and the JRE whether they are all IA32 or all Intel64 or if there is a mix - what the mix is?

I assume that if you run the command line idbc, it does come up?

One simple thing you could try, although I very much suspect that it will not help in this case, is to delete the ~/.idb subdirectory in your home directory. This directorycontains saved data on previous debug sessions. A corruption of this data could in theory lead to similar behavior.

Thanks, Rob

[Matthew_Foster]

That was the problem. The JDK I had installed was 32-bit, but I was sourcing the 64-bit environment for the compilers. I installed a 64-bit JDK, and idb comes right up.

Thanks Rob and Ron for all your help!

Matt