SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello Slackers;
I downloaded official eclipse binary and tried to launch eclipse by executing "./eclipse", but eclipse did not launch. "java" and "javac" are set to "/usr/lib/java/bin/".
Code:
phys@slackbox:~$ java -version
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Server VM (build 11.3-b02, mixed mode)
phys@slackbox:~$
Besides java itself, are there any other dependencies needed? I tried going through the log you provided, but it seems rather long-winded. Perhaps you might want to consider an eclipse package from either slacky.eu or a build script from slackbuilds.org ? You might have better luck that way, instead of just downloading the 'generic' from sun.
Thanks Jeebizz, I've installed "eclipse classic" using SBo slackbuild script, but still the same error message appears while launching program, then eclipse terminates. I have also tried to install older versions of JDK and JRE, nothing happened.
Code:
phys@slackbox:~$ eclipse
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb369398b, pid=23969, tid=3084114128
#
# Java VM: Java HotSpot(TM) Client VM (11.3-b02 mixed mode, sharing linux-x86)
# Problematic frame:
# C [libswt-mozilla-gtk-3452.so+0x1098b]
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid23969.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/usr/bin/eclipse: line 3: 23969 Aborted ./eclipse "$@"
phys@slackbox:~$
In the error log it seems eclipse is receiving SIGSEGV (Segmentation fault), so it doesn't look like a dependency problem at all but a program crash. It may be a problem with Java, but this is pure speculation.
Last edited by rg3; 04-18-2009 at 02:52 AM.
Reason: typo
yup! that's the one! are you using Slackware 12.2 or Slackware-current? There are some differences, you know!
Happy Slacking
I'm using slackware-current, I'll do some changes on the system to test what could be the causes. The eclipse's developers don't answer to my report...They suck!
I think there's something we're forgetting, guys...Downgrading a thing is not a solution to the problem, it exists and you won't solve just downgrading to another version, I'd call it "escaping". So the problem is not solved, it's still here and still exists, now...Let's do some changes on our system to understand where the error could be, and waiting to the eclipse team...(Waiting and hoping, eh?)
I just installed eclipse with the build from SlackBuilds.org on a clean 12.2+patches
system and it worked fine. Maybe there is an old plugin/workspace/config file that is
causing the problem.
I just installed eclipse with the build from SlackBuilds.org on a clean 12.2+patches
system and it worked fine. Maybe there is an old plugin/workspace/config file that is
causing the problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.