- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
[eclipse plugin] SIGBUS or SIGSEGV in libzip.so
Wed, 2009-10-28, 10:32
Hello,
I'm seeing a lot of segfault of the JVM in libzip.so when I use Eclipse
with the Scala plugin. They look like that :
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0xb5e61c53, pid=28222, tid=479632240
#
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode linux-x86 )
# Problematic frame:
# C [libzip.so+0xbc53]
#
# An error report file with more information is saved as:
# /home/farmand/java/workspaces/poiaze/cmdb/hs_err_pid28222.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.
#
It happens more often when Scala plugin is indexing, for example after
removing .metadata from the workspace.
I googled for that error, thinking that it was due to some broken
library in my Ubuntu 9.10 (it did happen with GTK in the past), but
found nothing interesting safe a message saying that it may be a
material problem (it doesn't seem so, memcheck is happy and I have no
other strange problem in my notebook, that moreover is only 3 months
old), a bug in an old JVM (I have the last 1.6 available), or something
with an eclipse plugin.
Does other people are seing that ? Is there a known workaround ?
Thanks !
--
Francois
Wed, 2009-10-28, 11:27
#2
Re: [eclipse plugin] SIGBUS or SIGSEGV in libzip.so
On Wed, 2009-10-28 at 10:32 +0100, Francois wrote:
> It happens more often when Scala plugin is indexing, for example after
> removing .metadata from the workspace.
>
> I googled for that error, thinking that it was due to some broken
> library in my Ubuntu 9.10 (it did happen with GTK in the past), but
> found nothing interesting safe a message saying that it may be a
> material problem (it doesn't seem so, memcheck is happy and I have no
> other strange problem in my notebook, that moreover is only 3 months
> old), a bug in an old JVM (I have the last 1.6 available), or something
> with an eclipse plugin.
>
> Does other people are seing that ? Is there a known workaround ?
That does look like a library combination bug, but hard to tell. If it's
not in the Sun database, maybe you should submit it to them and see what
they say.
Best,
Ismael
Wed, 2009-10-28, 11:47
#3
Re: [eclipse plugin] SIGBUS or SIGSEGV in libzip.so
On Wed, Oct 28, 2009 at 9:32 AM, Francois wrote:
> I'm seeing a lot of segfault of the JVM in libzip.so when I use Eclipse with
> the Scala plugin. They look like that :
> Does other people are seing that ? Is there a known workaround ?
I've not see it. You should check against Sun's bug database and report it.
As a workaround, you could try using the server compiler rather than the client.
Cheers,
Miles
Wed, 2009-10-28, 12:07
#4
Re: [eclipse plugin] SIGBUS or SIGSEGV in libzip.so
On 28/10/2009 11:19, Ismael Juma wrote:
> That does look like a library combination bug, but hard to tell. If it's
> not in the Sun database, maybe you should submit it to them and see what
> they say.
I've already looked, and all what I can find is about Jars changed when
used (for ex: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6236070)
Perhaps it's something like that involved, with maven updating things,
Scala plugin indexing others, and caches somewhere in Eclipse... Really
hard to tell, I didn't find any reproducible way of making it happens,
and I don't see it in simple projects :/ But when it happens, sometimes
it happens three or four time in a row.
Launching eclipse with -clean seems to help, but not sure it's linked.
I will try to find more information, at least the thread is here if
other people meet this error.
--
Francois
On Wednesday 28 October 2009 12:32:13 Francois wrote:
> Hello,
>
> I'm seeing a lot of segfault of the JVM in libzip.so when I use Eclipse
> with the Scala plugin. They look like that :
From time to time I also have a crash in java.util.zip.ZipFile.getNextEntry
(linux-amd64 is in use) - regardless Eclipse. Have not noticed any regularity.
Both with Sun JDK and OpenJDK. But it seems with GTK L&F it is more frequent
rather with Nimbus one.
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGBUS (0x7) at pc=0xb5e61c53, pid=28222, tid=479632240
> #
> # JRE version: 6.0_16-b01
> # Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode linux-x86 )
> # Problematic frame:
> # C [libzip.so+0xbc53]
> #
> # An error report file with more information is saved as:
> # /home/farmand/java/workspaces/poiaze/cmdb/hs_err_pid28222.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.
> #
>
> It happens more often when Scala plugin is indexing, for example after
> removing .metadata from the workspace.
>
> I googled for that error, thinking that it was due to some broken
> library in my Ubuntu 9.10 (it did happen with GTK in the past), but
> found nothing interesting safe a message saying that it may be a
> material problem (it doesn't seem so, memcheck is happy and I have no
> other strange problem in my notebook, that moreover is only 3 months
> old), a bug in an old JVM (I have the last 1.6 available), or something
> with an eclipse plugin.
>
> Does other people are seing that ? Is there a known workaround ?
>
> Thanks !
>
> --
> Francois
>