openjdk team mailing list archive
-
openjdk team
-
Mailing list archive
-
Message #01952
[Bug 373712] Re: eclipse c++ ganymede crashes when first opening and in essence wont open
Found related bugs in globalmenu tracker:
http://code.google.com/p/gnome2-globalmenu/issues/detail?id=436
http://code.google.com/p/gnome2-globalmenu/issues/detail?id=408
Seems to be a 64bit multi-threading problem in globalmenu.
** Bug watch added: code.google.com/p/gnome2-globalmenu/issues #436
http://code.google.com/p/gnome2-globalmenu/issues/detail?id=436
** Bug watch added: code.google.com/p/gnome2-globalmenu/issues #408
http://code.google.com/p/gnome2-globalmenu/issues/detail?id=408
--
eclipse c++ ganymede crashes when first opening and in essence wont open
https://bugs.launchpad.net/bugs/373712
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.
Status in “openjdk-6” source package in Ubuntu: New
Bug description:
eclipse c++ ganymede crashes when first opening and in essence wont open
when i run it from the launcher i created it just goes to the screen where it ask me what workspace i select it and then it goes to where it has a status bar where it normally does a lot of loading of java stuff but this time i see the bar and it just disappears when running through terminal i get this output
ps: i've included the error log as an attachment as it is very long
$/mapps/eclipse/eclipse
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f24d591b379, pid=4662, tid=139796832033104
#
# Java VM: OpenJDK 64-Bit Server VM (14.0-b08 mixed mode linux-amd64 )
# Distribution: Ubuntu 9.04, package 6b14-1.4.1-0ubuntu7
# Problematic frame:
# C [libgobject-2.0.so.0+0xf379] g_object_ref+0x9
#
# An error report file with more information is saved as:
# /home/kurt/hs_err_pid4662.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
References