1 |
On Thu, Jan 27, 2011 at 04:19:18PM -0600, Paul Hartman wrote: |
2 |
> On Fri, Jan 21, 2011 at 5:57 AM, Fernando Boaglio <boaglio@×××××.com> wrote: |
3 |
> > Hi, |
4 |
> > |
5 |
> > There is a recent update which broke my Java IDE (Eclipse - not from |
6 |
> > portage) . |
7 |
> > |
8 |
> > I've seen this strange behavior in 2 different machines, both ADM64, but I'm |
9 |
> > not sure which package should I inform to this error: |
10 |
> > |
11 |
> > |
12 |
> > *** glibc detected *** /opt/sun-jdk-1.6.0.23/bin/java: free(): invalid |
13 |
> > pointer: 0x00000000456f30d0 *** |
14 |
> > ======= Backtrace: ========= |
15 |
> > /lib/libc.so.6(+0x783c6)[0x7f7c039593c6] |
16 |
> > /opt/sun-jdk-1.6.0.23/jre/lib/amd64/server/libjvm.so(+0x61b879)[0x7f7c0341a879] |
17 |
> > /opt/sun-jdk-1.6.0.23/jre/lib/amd64/server/libjvm.so(+0x43d44f)[0x7f7c0323c44f] |
18 |
> > /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] |
19 |
> > [0x7f7bfebeaca8] |
20 |
> |
21 |
> > Is it glibc ? |
22 |
> |
23 |
> glibc is reporting to you about the error, FYI you can control its |
24 |
> behavior (ignore, warn, abort) with the MALLOC_CHECK_ variable. See |
25 |
> "man malloc" and scroll to the last paragraph. Maybe running as root |
26 |
> operated under a different malloc mode? |
27 |
> |
28 |
> Looks like maybe your file |
29 |
> /home/fb/eclipseWTP3.2.3/configuration/org.eclipse.osgi/bundles/151/1/.cp/libswt-pi-gtk-3657.so |
30 |
> is the common thread... |
31 |
> |
32 |
> I think the only way to really know exactly where it's crashing is to |
33 |
> build everything involved with debug symbols and debug the coredump or |
34 |
> use valgrind or something like that. If Eclipse is a binary install |
35 |
> then I guess report it to whoever makes it (I don't know anything |
36 |
> about Java or Eclipse). |
37 |
|
38 |
Given that in another email he mentioned that running eclipse as root |
39 |
doesn't crash, then it's more likely that the problem is due to the |
40 |
updating of various eclipse files in the user workspace. |
41 |
|
42 |
To confirm, just try starting eclipse with a different workspace, using |
43 |
the following (untested) |
44 |
$ eclipse -data /home/fb/eclipse_test_workspace |
45 |
|
46 |
Also compare |
47 |
/home/fb/eclipseWTP3.2.3/configuration/org.eclipse.osgi/bundles/151/1/.cp/libswt-pi-gtk-3657.so |
48 |
against |
49 |
/usr/lib64/eclipse/configuration/org.eclipse.osgi/bundles/151/1/.cp/libswt-pi-gtk-3657.so |
50 |
and see if the corresponding one on the system both exists and is the |
51 |
same. (particularly since this appears to be your problem file) |
52 |
|
53 |
I suspect not. I thought that updating of various core |
54 |
libraries/bundles of eclipse was disabled on most linux distros due to |
55 |
eclipse being built against the system version of glibc, but a update |
56 |
there is the only way I can think that it could go from working to |
57 |
crashing after an eclipse update. |
58 |
|
59 |
-- |
60 |
Darragh |
61 |
|
62 |
"Nothing is foolproof to a sufficiently talented fool." |