From owner-freebsd-java@FreeBSD.ORG Tue Mar 15 17:22:05 2005 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88D9116A4CE for ; Tue, 15 Mar 2005 17:22:05 +0000 (GMT) Received: from mrelay3.uni-hannover.de (mrelay3.uni-hannover.de [130.75.2.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3FF443D39 for ; Tue, 15 Mar 2005 17:22:04 +0000 (GMT) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2])j2FHM19e029351 for ; Tue, 15 Mar 2005 18:22:01 +0100 (MET) Received: by www.pmp.uni-hannover.de (Postfix, from userid 846) id 064C42DD; Tue, 15 Mar 2005 18:21:57 +0100 (CET) Date: Tue, 15 Mar 2005 18:21:56 +0100 From: Gerrit =?iso-8859-1?Q?K=FChn?= To: freebsd-java@freebsd.org Message-ID: <20050315172156.GA98027@pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.2.2 (mrelay3.uni-hannover.de [130.75.2.41]); Tue, 15 Mar 2005 18:22:01 +0100 (MET) X-Scanned-By: MIMEDefang 2.42 Subject: Eclipse hangs at splashscreen X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 17:22:05 -0000 Hi folks, I've had this problem months before: Eclipse displays the splashscreen when starting, but after that nothing more happens. The java process remains in state "kserel". I can kill eclipse, which makes the splash go away, but the java process remains (in state "STOP" now) forever. Back then this was caused by mixed threading libs (at least I thought so), and I could make work by setting up an appropriate libmap.conf. However, about two weeks ago I suddenly saw this behaviour again. Well, meanwhile I did two gnome-updates, one kde-update, one perl-update and some smaller updates on this machine, so I think the threading-lib problem is not an issue anymore (at least I cannot find old links using ldd on randomly chosen binaries). So I gave it a try without libmap and with different entries than I used before (libkse, libc_r, libpthread, I tried each and every combination). Strange enough, it /sometimes/ worked for some startups of eclipse, but then went back to the behaviour described above, so maybe the reason lies elsewhere?! Just to make sure, I recompiled eclipse with portupgrade -R -f, but the problem is still there. Meanwhile, I havn't been able to start eclipse for two days (and I tried it quite a lot of times :-). This is the only machine where I see this problem. I have several other machines here (running 5.2.1 and 5.3-stable), which all work fine. The one with the problem is running 5.3-STABLE, latest eclipse and jdk14 from ports. However, the only real difference to the other boxes may be that it's an SMP station (2 x P3-933). Are there any hints how to get eclipse started on this machine again? I'd really like to do my software development on it, because it has plenty of RAM and is the fastest box around. cu Gerrit --