From owner-freebsd-eclipse@FreeBSD.ORG Mon Dec 26 11:02:10 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3197816A420 for ; Mon, 26 Dec 2005 11:02:10 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2DC543D5F for ; Mon, 26 Dec 2005 11:02:09 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBQB298P018013 for ; Mon, 26 Dec 2005 11:02:09 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBQB28LG018007 for freebsd-eclipse@freebsd.org; Mon, 26 Dec 2005 11:02:08 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 26 Dec 2005 11:02:08 GMT Message-Id: <200512261102.jBQB28LG018007@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-eclipse@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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, 26 Dec 2005 11:02:10 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/11/10] ports/88777 eclipse eclipse crashes java machine on indexing 1 problem total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/12/03] ports/89893 eclipse [patch] update java/eclipse-cdt to versio 1 problem total. From owner-freebsd-eclipse@FreeBSD.ORG Tue Dec 27 18:03:47 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2017D16A437 for ; Tue, 27 Dec 2005 18:03:47 +0000 (GMT) (envelope-from micahjon@ywave.com) Received: from smtpout1.ywave.com (ycomradius.yelmtel.com [216.227.100.60]) by mx1.FreeBSD.org (Postfix) with SMTP id 84CDE43DAC for ; Tue, 27 Dec 2005 18:03:35 +0000 (GMT) (envelope-from micahjon@ywave.com) Received: (qmail 24177 invoked by uid 502); 27 Dec 2005 18:03:33 -0000 Received: from dsl-12-178-97-72.ywave.com (HELO ?192.168.1.65?) (micahjon@ywave.com@12.178.97.72) by 0 with SMTP; 27 Dec 2005 18:03:33 -0000 X-CLIENT-IP: 12.178.97.72 X-CLIENT-HOST: dsl-12-178-97-72.ywave.com Message-ID: <43B181F4.6060400@ywave.com> Date: Tue, 27 Dec 2005 10:03:32 -0800 From: Micah User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051224) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-eclipse@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Help with diagnosing eclipse freezes 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: Tue, 27 Dec 2005 18:03:47 -0000 Hey List, I asked a similar question back in November. See http://lists.freebsd.org/mailman/htdig/freebsd-eclipse/2005-November/000210.html A quick rehash: Starting eclipse via the command line "eclipse" takes ~3.5 minutes to start. Creating a new java project and a new class and then moving the cursor resulted in a 1 minute freeze. After it unfroze typing "System." caused the IDE to freeze for another minute. The times seem to be fairly consistent. This is on an Athlon 64 3000+ system with 1.5GB ram running FreeBSD-release 6.0 i386 with the generic kernel. I'm currently trying to run eclipse-3.1.1_2, but it happened on 3.1.1 and 3.1_3 as well. A top indicates that "java" is taking up all available processor time. No disk activity is indicated in systat or by the drive LED on the case. Poseidon, the other largish java application I use frequently, does not exhibit these freezes. Since November I've upgraded to FreeBSD 6.0 release, tried compiling eclipse with JDK15, tried compiling with JDK14, and tried the packaged version from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All/eclipse-3.1.1_2.tbz. JDK15 fails to start crashing with a java hotspot zlib error. JDK14 and packaged both exhibit the same freezes. I'm not sure how to begin diagnosing this. Help with the debugger, eclipse debugging flags, or tools to watch the system during the freezes would be most appreciated. Thanks, Micah From owner-freebsd-eclipse@FreeBSD.ORG Fri Dec 30 05:18:48 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F48516A41F for ; Fri, 30 Dec 2005 05:18:48 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from mail.droso.net (koala.droso.net [193.88.12.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3C2C43D5C for ; Fri, 30 Dec 2005 05:18:47 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by mail.droso.net (Postfix) with ESMTP id 5175922B12 for ; Fri, 30 Dec 2005 06:18:46 +0100 (CET) Received: from koala.ipv6.droso.net (localhost [IPv6:::1]) by mail.droso.net (Postfix) with ESMTP id B10A622B21 for ; Fri, 30 Dec 2005 06:18:42 +0100 (CET) From: linimon@FreeBSD.org To: freebsd-eclipse@freebsd.org Message-Id: <20051230051842.B10A622B21@mail.droso.net> Date: Fri, 30 Dec 2005 06:18:42 +0100 (CET) X-Virus-Scanned: by amavisd 0.1 Subject: FreeBSD ports that you maintain which are currently marked broken 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: Fri, 30 Dec 2005 05:18:48 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we are attempting to notify maintainers of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc3.4, which is much stricter about such things as function declarations, literal strings constants that continue over several physical lines, and forcing the deprecation of antique header files such as varargs.h (we should now be using stdargs.h). The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. If you need help in one or more build environments that you do not have access to, please ask for help on the freebsd-ports mailing list. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 4.x/5.x/6.x with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: java/eclipse-viplugin broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=eclipse-viplugin If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD.