Bugzilla Bug 67341

After emerging eclipse-sdk-3.0.1-r1 on amd64 (I've tried both sun-jdk-1.5.0 and
blackdown 1.4.2), I get a segmentation fault when trying to start eclipse-3.

Reproducible: Always
Steps to Reproduce:
1. Emerge eclipse-sdk
2. run eclipse-3
3. Also java -cp startup.jar org.eclipse.core.launcher.Main

Actual Results:  
/usr/bin/eclipse-3: line 36:  6935 Segmentation fault      ${ECLIPSE_BIN} $*

Expected Results:  
eclipse starts normally

Portage 2.0.50-r11 (gcc34-amd64-2004.1, gcc-3.4.2, glibc-2.3.4.20040808-r1,
2.6.
8-gentoo-r4)
=================================================================
System uname: 2.6.8-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 2800+
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-march=athlon64 -mtune=athlon64 -O3 -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.3
/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config
/us
r/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon64 -mtune=athlon64 -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache"
GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/
ftp://mirror.nutsmaas.nl/ge
ntoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X amd64 apm arts avi berkdb bitmap-fonts crypt cups encode esd f77
foomatic
db gdbm gif gnome gpm gtk gtk2 imlib jpeg kde libg++ libwww mikmod mozilla mpeg
mysql ncurses nls oci8 oggvorbis opengl oss pam pdflib perl png ppds python qt
q
uicktime readline samba sdl slang spell ssl tcpd truetype xml2 xmms xprint xv
zl ib"

Stacktrace reveals that problem occurs in strdup() call in fixEnvForMozilla().
Since I am still looking into how to get my own patch into an ebuild, I have
not verified this yet, but the problem may be because there are no prototypes
for getenv() which introduces conversions from 64 to 32 back to 64.
It seems possible to avoid the problem by making sure environment variables
MOZILLA_FIVE_HOME and LD_LIBRARY_PATH are not set when starting eclipse.

Adding include file stdlib.h to files using getenv() seems to do the trick.

Created an attachment (id=42127) [details]
Suggestion of new ebuild and patch to fix 64bit problems with getenv()

I do have some amateur version of a new ebuild with patch and digest. I am
attaching it here in case it can be useful to someone.

Okay, thanks! I will apply this and have the amd64 people test it.

I experienced the same problem.
The stated workaround (unset of MOZILLA_FIVE_HOME and LD_LIBRARY_PATH) worked.
I haven't really used the program so I don't know if something else is broken.

Waiting for a fixed version so I can test it.

Same issue here.  Resolved by running: 
unset MOZILLA_FIVE_HOME;
eclipse-3

Committed.