idb crashes on Arch Linux with openjdk java

idb crashes on Arch Linux with openjdk java

Hi,

I have a problem with idb. It works as expected when run as root, but when run as normal user i get this error message, after a crash, upon loading the executable, and sometimes even before that.

The error message is:

#############################

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f4ad376f1ae, pid=30033, tid=139960566785792
#
# JRE version: OpenJDK Runtime Environment (7.0_45-b31) (build 1.7.0_45-b31)
# Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libgtk-x11-2.0.so.0+0x2481ae]  gtk_widget_set_tooltip_text+0x1e
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/davide/svn-repo/fluidSOS/rotatingCouetteModel/soton-solver-mixed-fd-spectral-method/hs_err_pid30033.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
#
/opt/intel/composer_xe_2013_sp1.1.106/bin/intel64/idb: line 75: 30033 Aborted                 (core dumped) java -jar $INSTALLDIR/debugger/gui/intel64/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -showsplash -gui -native $TTY $IDB_ARGUMENTS
There were problems starting IDB.
This usually indicates Java Runtime or library compatibility issues.
Please check your environment.
For details check the log file at /home/davide/.idb_13.0_linux_intel64_app/workspace/.metadata/.log.

######################################

The log file indicated contains:

######################################

!SESSION 2014-01-10 12:01:02.544 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_45
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
Framework arguments:  -gui -native -tty /dev/tty
Command-line arguments:  -gui -native -tty /dev/tty

!ENTRY org.eclipse.equinox.registry 2 0 2014-01-10 12:01:03.247
!MESSAGE The extensions and extension-points from the bundle "com.intel.debugger.ui.nl1" are ignored. The bundle is not marked as singleton.

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.269
!MESSAGE NLS unused message: ActionManager_deleteBreakpointAll in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.272
!MESSAGE NLS unused message: ActionManager_deleteBreakpointAllDesc in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.272
!MESSAGE NLS unused message: ActionManager_suspendDesc in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.272
!MESSAGE NLS unused message: ActionManager_interruptDesc in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.273
!MESSAGE NLS unused message: ActionManager_openPagingWindow in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.273
!MESSAGE NLS unused message: ActionManager_openSvenTriggerWindow in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.273
!MESSAGE NLS unused message: ActionManager_SearchSourceFile in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS unused message: ActionManager_suspend in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS unused message: ActionManager_interrupt in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS unused message: ActionManager_openAddressTranslationDialog in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS missing message: ActionManager_kill in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS missing message: ActionManager_killDesc in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.275
!MESSAGE NLS missing message: ActionManager_loadBatchFile in: com.intel.debugger.ui.messages

######################################

As I said i can use the debugger by launching it as root but it is just a workaround.

Any help appreciated.

Regards,

Davide

 

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

Dear Davide,

although we don't explicitly validate against OpenJDK Runtime Environment (7.0_45-b31) (build 1.7.0_45-b31), I suspect that this is not a compatibility issue, but rather a JRE install/configuration issue. I suspect that it is not resgistered correctly for non-root use and our debugger does not find some of the JRE definitions it is looking for when setting up the GUI.

Let me ask 1 or 2 additioanl questions to try and narrow it down:

Do you have multiple JREs installed on your system? Is the JRE that is being called when starting IDB as root the same one as listed above?

I think the next steps may be to

- ensure the JRE is in your user seach path

- reinstall the JRE from the OS package mananger

- install the latest JRE from www.java.com directly

If none of these 3 items improves the behavior we need to have a closer look at the issue. When I see the exact symptoms you are describing they are usually related to JRE path/regsitration issues though.

 

Thanks, Rob

 

 

Hello,

I'd like to add that:
1. If you use Eclipse (http://www.eclipse.org), do you see the same error? The reason for this is to check whether this is an issue with the Eclipse framework that we use for IDB. In that case it would be a general issue.
2. Maybe you already have used IDB with an older version. You could remove the IDB configuration directories in your $HOME (that is ~/.idb*); or you create a new user and try IDB there. Root might work because there are no old configuration files lying around.

Please let us know about the outcome.

Thank you & best regards,

Georg Zitzlsberger

Hi,

Thanks for the precious input.

I used an older version of idb and this might cause the issue as Georg argued. However, i am away from my machine for a couple of weeks and I am not able to check. I will let you know about the outcome.

Regards,

Davide Lasagna

 

Hi,

   I have almost exactly the same problem as Davide L. except in all modes, user,root 

# Problematic frame:
# C  [libgtk-x11-2.0.so.0+0x2481ae]  gtk_widget_set_tooltip_text+0x1e
 

I have tried OpenJDK 1.7.0 -- 1.8.0 and Sun java 1.8.0. My Eclipse works perfect.

I am using Fedora20. The one difference I see is ide uses org.eclipse.equinox.launcher_1.2.0.v20110502.jar

and Eclipse uses org.eclipse.equinox.launcher_1.3.0.v20131104-1241.jar.

Could this be the problem?

The rest of the Parallel Studio is also very unstable. Never had so many problems. It usually worked flawlessly. Got some bugs out by compiling gdb 7.7. Tried a new compile of glib-2.39.92, nothing changed.

Any suggestions?

Dancie

Dear Dancie,

IDB is not being fully validated agsinst the very latest Fedora 20 and JRE 1.8 combination as we now focus more on our own build of GDB with Intel architecture specific extensions, that you may have noticed when you installed the latest Intlel(R) Parallel Studio XE.

That said, for the specific IDB GUI issue, could you run a quick test for me and check if downgrading to the Sun Java JRE 1.6 from http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase6-419409.html

resolves the issue?

That would let us know, if the incompatibility is with the latest JRE version. I have a suspicion that the problem lies there.

Thanks, Rob

Thanks Rob for a quick reply,

Gave it a try but the same results. -------

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000000303c48447e, pid=5391, tid=140447486789376
#
# JRE version: 6.0_45-b06
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.45-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libgtk-x11-2.0.so.0+0x28447e]  __float128+0x1e

./idb: line 75:  5391 Aborted                 (core dumped) java -jar $INSTALLDIR/debugger/gui/intel64/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -showsplash -gui -native $TTY $IDB_ARGUMENTS

 

 

the same error comes back --  [libgtk-x11-2.0.so.0+0x28447e]  __float128+0x1e

Every java version gives the same result.

I went as far back as java 1.5.0. This version almost worked. Everything came up until I loaded an executable then it hung.

I appreciate the help. It hasen't helped idb BUT -- with This version of java all the rest of the Intel -- Inspector, VTune,etc began to be very stable

This actually fixed the major problem I was having. 

I think that the idb problem  has something to do with libgtk-x11.

I think I'll will put this problem away for a while. Can work good with the rest.

Thanks

Dancie

Hi Davide,

this means that it is not the Java JRE, but Fedora 20 itself that causes the incompatibility. I can file a defect for you against this, but with the ongoing migration of our efforts to improve GDB instead of investing into IDB, I don't know if we can promise Fedora 20 compatibility - sorry :-(.

Rob

Hi all,

I solved my problem on my Arch Linux machine. It turned out to be a problem with the gtk theme I was using and nothing else. I use KDE as desktop environment and OxygenGTK as the theme for gtk applications. Changing gtk theme to any other theme solved the problem, so as Rob suggested it is not a JRE issue. In fact, the root user has different theme setting so it worked when launching idb as super user.

Regards,

Davide

Thanks Davide!

great to know that it is not a JRE issue, but GTK theme specifc.

Rob

Login to leave a comment.