Summary: The Java VM running Eclipse on my system appears to be working, but internally it gets segfaults constantly.
Steps to reproduce:
- Extract it as
set follow-fork childso that GDB will trace the actual Java process and not just the Eclipse launcher.
runto start Eclipse. You might have to select a workspace directory.
- You should get a segmentation fault (SIGSEGV) pretty soon. Type
contin GDB and you will get another. Type
contagain and you will get another. And so on ad nauseam.
Again, Eclipse appears to be working, presumably because it is catching the signal and recovering somehow.
My OS is 64-bit Red Hat Enterprise Linux 6.5 with all updates as of yesterday (2014-May-22). The Java RPM is
java-1.7.0-openjdk-18.104.22.168-22.214.171.124.el6_5.x86_64, the current release (Version 7 Update 55) from http://java.com/ produces the same results.
I am curious to know whether this behavior happens for other people and on other flavors of Linux. More importantly, I am curious if anybody knows whether this is "normal".
(In case you are wondering... Although Eclipse appears to be working, I am concerned that some real problem is being hidden. I noticed this because I am getting occasional, not-entirely-reproducible segfaults in a plug-in that uses WebKit. I thought I would try to observe the segfault under GDB, but this turns out to be tricky because the JVM is segfaulting over and over right from the beginning, even on a fresh install without the offending plug-in.)