List Archive: gentoo-amd64
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Thu, Jan 27, 2011 at 04:19:18PM -0600, Paul Hartman wrote:
> On Fri, Jan 21, 2011 at 5:57 AM, Fernando Boaglio <boaglio@...> wrote:
> > Hi,
> > There is a recent update which broke my Java IDE (Eclipse - not from
> > portage) .
> > I've seen this strange behavior in 2 different machines, both ADM64, but I'm
> > not sure which package should I inform to this error:
> > *** glibc detected *** /opt/sun-jdk-220.127.116.11/bin/java: free(): invalid
> > pointer: 0x00000000456f30d0 ***
> > ======= Backtrace: =========
> > /lib/libc.so.6(+0x783c6)[0x7f7c039593c6]
> > /opt/sun-jdk-18.104.22.168/jre/lib/amd64/server/libjvm.so(+0x61b879)[0x7f7c0341a879]
> > /opt/sun-jdk-22.214.171.124/jre/lib/amd64/server/libjvm.so(+0x43d44f)[0x7f7c0323c44f]
> > /home/fb/eclipseWTP3.2.3/configuration/org.eclipse.osgi/bundles/151/1/.cp/libswt-pi-gtk-3657.so(Java_org_eclipse_swt_internal_gtk_OS__1g_1data_1input_1stream_1read_1line+0xe7)[0x7f7bf5267d04]
> > [0x7f7bfebeaca8]
> > Is it glibc ?
> glibc is reporting to you about the error, FYI you can control its
> behavior (ignore, warn, abort) with the MALLOC_CHECK_ variable. See
> "man malloc" and scroll to the last paragraph. Maybe running as root
> operated under a different malloc mode?
> Looks like maybe your file
> is the common thread...
> I think the only way to really know exactly where it's crashing is to
> build everything involved with debug symbols and debug the coredump or
> use valgrind or something like that. If Eclipse is a binary install
> then I guess report it to whoever makes it (I don't know anything
> about Java or Eclipse).
Given that in another email he mentioned that running eclipse as root
doesn't crash, then it's more likely that the problem is due to the
updating of various eclipse files in the user workspace.
To confirm, just try starting eclipse with a different workspace, using
the following (untested)
$ eclipse -data /home/fb/eclipse_test_workspace
and see if the corresponding one on the system both exists and is the
same. (particularly since this appears to be your problem file)
I suspect not. I thought that updating of various core
libraries/bundles of eclipse was disabled on most linux distros due to
eclipse being built against the system version of glibc, but a update
there is the only way I can think that it could go from working to
crashing after an eclipse update.
"Nothing is foolproof to a sufficiently talented fool."