[Bug 734726] New: Eclipse Indigo gives "glibc: Invalid pointer" with Android ADT in SuSE 12.1 x86_64
https://bugzilla.novell.com/show_bug.cgi?id=734726 https://bugzilla.novell.com/show_bug.cgi?id=734726#c0 Summary: Eclipse Indigo gives "glibc: Invalid pointer" with Android ADT in SuSE 12.1 x86_64 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: johanp@aditus.nu QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2 System: Linux x64 (OpenSuse 12.1) Java: Sun Java 1.6u29 (same with OpenJDK 1.6.0) Eclipse Version: 3.7.1 Eclipse Build id: M20110909-1335 ADT r15.0.1 SDK (Any) Description: After a clean install of Eclipse Indigo with Android development kit It is very easy to provoke a "Invalid pointer crash in glibc". This does not happen in OpenSuSE 11.4 hence this report agains SuSE. It seems glibc is detecting an invalid pointer when run as a normal user but this works fine when run as root. The first lines of the stack trace is shown below (in this case the Sun Java 1.6u29 was used but the exact same behavior can be seen with Open JDK 1.6.0) *** glibc detected *** /usr/bin/java: free(): invalid pointer: 0x0000000040cb3700 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x74c06)[0x7f4c36776c06] /opt/java/64/jre1.6.0_29/lib/amd64/server/libjvm.so(+0x7082e9)[0x7f4c361ff2e9] /opt/java/64/jre1.6.0_29/lib/amd64/server/libjvm.so(+0x513f9f)[0x7f4c3600af9f] /usr/local/share/eclipse/configuration/org.eclipse.osgi/bundles/154/1/.cp/libswt-pi-gtk-3738.so(Java_org_eclipse_swt_internal_gtk_OS__1g_1data_1input_1stream_1read_1line+0xe7)[0x7f4c290dfd10] Reproducible: Always Steps to Reproduce: 1. Install Eclipse Indigo and install Android ADT 2. Run eclipse as a normal user 3. Create a new Android project 4. Try to expand the project in the menu -> eclipse crashes with a glibc: Invalid pointer This can alternatively be reproduced again by open the "Help->About Eclipse SDK->Installation details, Tap configuration Tab, Click "View Error Log" button. The same crash happens again. I'm reporting this against SuSE 12.1 64bit since this problem can not be reproduced in SuSE 11.4 32bit If Eclipse is started as root the "glibc: Invalid pointer error" does not happen Actual Results: glibc: Invalid pointer Expected Results: That Eclipse expands the menu as requested - Problem does not happen with SuSE 11.4 (neither 32 nor 64 bit) - If reverting to Eclipse Helios (previous version) the problem does not happen -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=734726 https://bugzilla.novell.com/show_bug.cgi?id=734726#c1 --- Comment #1 from Johan Persson <johanp@aditus.nu> 2011-12-03 20:00:31 UTC --- In addition this is specific for SuSE 12.1 x86_64 since this crash does not happen on plain 32bit SuSE 12.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=734726 https://bugzilla.novell.com/show_bug.cgi?id=734726#c zj jia <zjjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |matz@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=734726 https://bugzilla.novell.com/show_bug.cgi?id=734726#c2 --- Comment #2 from Marcus Meissner <meissner@suse.com> 2011-12-04 15:23:29 UTC --- its the malloc debugging which we will disable by a aaa_base update rm /etc/profile.d/malloc-debug.* and either reboot or do once: export -n MALLOC_DEBUG_ unset MALLOC_DEBUG_ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=734726 https://bugzilla.novell.com/show_bug.cgi?id=734726#c3 --- Comment #3 from Johan Persson <johanp@aditus.nu> 2011-12-04 18:20:37 UTC --- I have no malloc-debug.* in my profile directory. But tha lead me to checking if I had the MALLOC_CHECK_ set to a value other than 0 in my environment. and look and behold ~> env | grep MALLOC MALLOC_CHECK_=3 MALLOC_PERTURB_=69 so doing a ~>export MALLOC_CHECK_=0 made this problem go away (well, rather hide, there is still a on obvious heap corruption in INDIGO) However, the big question now is where does malloc_check_ get the '3' value set? This is not done by any of my startup script (double checked). (I wan't even aware there was a '3' value I only thought you could use 0,1,2 Do you know where this is set I just assume that MALLOC_PERTURB_=69 is just a random value to fill the heap with to be able to recognize the value at debugging. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=734726 https://bugzilla.novell.com/show_bug.cgi?id=734726#c4 Johan Persson <johanp@aditus.nu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Johan Persson <johanp@aditus.nu> 2011-12-04 19:49:15 UTC --- My bad. I forgot I had run a system update but not yet restarted so the changes hadn't been applied. This solves the problem (or at least the symptoms). Will close this as fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com