1 |
On Fri, Jan 21, 2011 at 5:57 AM, Fernando Boaglio <boaglio@×××××.com> wrote: |
2 |
> Hi, |
3 |
> |
4 |
> There is a recent update which broke my Java IDE (Eclipse - not from |
5 |
> portage) . |
6 |
> |
7 |
> I've seen this strange behavior in 2 different machines, both ADM64, but I'm |
8 |
> not sure which package should I inform to this error: |
9 |
> |
10 |
> |
11 |
> *** glibc detected *** /opt/sun-jdk-1.6.0.23/bin/java: free(): invalid |
12 |
> pointer: 0x00000000456f30d0 *** |
13 |
> ======= Backtrace: ========= |
14 |
> /lib/libc.so.6(+0x783c6)[0x7f7c039593c6] |
15 |
> /opt/sun-jdk-1.6.0.23/jre/lib/amd64/server/libjvm.so(+0x61b879)[0x7f7c0341a879] |
16 |
> /opt/sun-jdk-1.6.0.23/jre/lib/amd64/server/libjvm.so(+0x43d44f)[0x7f7c0323c44f] |
17 |
> /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] |
18 |
> [0x7f7bfebeaca8] |
19 |
|
20 |
> Is it glibc ? |
21 |
|
22 |
glibc is reporting to you about the error, FYI you can control its |
23 |
behavior (ignore, warn, abort) with the MALLOC_CHECK_ variable. See |
24 |
"man malloc" and scroll to the last paragraph. Maybe running as root |
25 |
operated under a different malloc mode? |
26 |
|
27 |
Looks like maybe your file |
28 |
/home/fb/eclipseWTP3.2.3/configuration/org.eclipse.osgi/bundles/151/1/.cp/libswt-pi-gtk-3657.so |
29 |
is the common thread... |
30 |
|
31 |
I think the only way to really know exactly where it's crashing is to |
32 |
build everything involved with debug symbols and debug the coredump or |
33 |
use valgrind or something like that. If Eclipse is a binary install |
34 |
then I guess report it to whoever makes it (I don't know anything |
35 |
about Java or Eclipse). |