From owner-freebsd-eclipse@FreeBSD.ORG Mon May 9 18:35:25 2011 Return-Path: Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E6D71065670 for ; Mon, 9 May 2011 18:35:25 +0000 (UTC) (envelope-from c47g@gmx.at) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id D7D6E8FC15 for ; Mon, 9 May 2011 18:35:24 +0000 (UTC) Received: (qmail invoked by alias); 09 May 2011 18:35:23 -0000 Received: from cm203-32.liwest.at (EHLO bones.gusis.at) [81.10.203.32] by mail.gmx.net (mp034) with SMTP; 09 May 2011 20:35:23 +0200 X-Authenticated: #9978462 X-Provags-ID: V01U2FsdGVkX19wqRsNBnFwhV+eiddHTG6CB3A83X4KUcvQSvzJMy R+IG74wTaQTAoh From: Christian Gusenbauer To: Brandon Gooch Date: Mon, 9 May 2011 20:35:33 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-CURRENT; KDE/4.6.2; amd64; ; ) References: <201105091735.36939.c47g@gmx.at> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201105092035.33964.c47g@gmx.at> X-Y-GMX-Trusted: 0 Cc: freebsd-eclipse@freebsd.org Subject: Re: eclipse crashes on current/amd64 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2011 18:35:25 -0000 Hi Brandon! On Monday 09 May 2011 19:00:59 Brandon Gooch wrote: > On Mon, May 9, 2011 at 10:35 AM, Christian Gusenbauer wrote: > > Hi! > > > > I'm quite new to the Java world, but I'd like to learn Java, so I > > thought, I give eclipse a chance and compiled/installed it. After > > starting eclipse I clicked on the "javadoc" tab in the bottom half of > > the eclipse window and after a few seconds eclipse crashed :-(. > > I'm a newb myself, and just began working with eclipse (and Java). I'm > experiencing similar crashes. > > I haven't done any debugging of the issue, but I found a work-around: > > $ eclipse -vmargs -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null > > or setting it in eclipse.ini (somewhere after the -vmargs line): > > cat /usr/local/lib/eclipse/eclipse.ini > [SNIP] > -vmargs > -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null > [SNIP] > > ...works for me. What it does EXACTLY is unknown to me at this point, > although I assume it's disabling whatever functionality it would > otherwise obtain from libxul (perhaps using some other method of > detecting the components required, or using something internally). > Great, that works for me, too :)! > > The core dump contains hundreds of > > > > #178 0x0000000847550595 in NS_GetComponentManager_P () > > from /usr/local/lib/libxul/libxul.so > > #179 0x0000000847550595 in NS_GetComponentManager_P () > > from /usr/local/lib/libxul/libxul.so > > #180 0x0000000847550595 in NS_GetComponentManager_P () > > from /usr/local/lib/libxul/libxul.so > > #181 0x0000000847550595 in NS_GetComponentManager_P () > > from /usr/local/lib/libxul/libxul.so > > > > entries and the top of the call stack looks like this: > > > > #1631 0x00007fffffbfd568 in ?? () > > #1632 0x000000080000000c in ?? () > > #1633 0x0000000806292080 in ?? () > > #1634 0x0000000802f3b5a0 in ?? () > > #1635 0x00007fffffbfd4e8 in ?? () > > #1636 0x00007fffffbfd3d0 in ?? () > > #1637 0x000000080184dbc2 in JavaCalls::call_helper () > > from /data/local/openjdk6/jre/lib/amd64/server/libjvm.so > > Previous frame inner to this frame (corrupt stack?) > > > > So what's up with eclipse/libxul? > > > > Thanks, > > Christian. > > I'm actually seeing the JVM crash (java.core is generated), so perhaps > the subtleties of our issues differ a bit, but let me know if the > above suggestion works. Well I think the crashes we experience are the same :-). Good to know, that I'm not alone ;-)! > > Thanks! > > -Brandon Thanks for your help, Christian.