From owner-freebsd-java Wed Mar 20 7: 9:46 2002 Delivered-To: freebsd-java@freebsd.org Received: from rhymer.cogsci.ed.ac.uk (rhymer.cogsci.ed.ac.uk [129.215.144.8]) by hub.freebsd.org (Postfix) with ESMTP id 8FB1F37B41A for ; Wed, 20 Mar 2002 07:09:35 -0800 (PST) Received: from sorley.cogsci.ed.ac.uk (sorley [129.215.144.53]) by rhymer.cogsci.ed.ac.uk (8.9.3/8.9.3) with ESMTP id PAA07999 for ; Wed, 20 Mar 2002 15:09:33 GMT Received: (from richard@localhost) by sorley.cogsci.ed.ac.uk (8.9.3+Sun/8.9.3) id PAA29782 for java@FreeBSD.ORG; Wed, 20 Mar 2002 15:09:32 GMT Date: Wed, 20 Mar 2002 15:09:32 GMT Message-Id: <200203201509.PAA29782@sorley.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: Mozilla core dump with plugin To: java@FreeBSD.ORG In-Reply-To: Bill Huey's message of Wed, 20 Mar 2002 02:09:52 -0800 Organization: just say no Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Just curious, what methodology did you use to track this down ? "Reading the error messages". It turned out that Mozilla was printing out a stack backtrace before dying, which I didn't see at first because it was going to /dev/ttyv0 (I started mozilla from a twm menu). It was fairly easy to track down the function in question, and then it was just a matter of staring at the code. It would have been a lot quicker if I could work out how to rebuild just the (very small) relevant parts of the JDK after making an edit, rather than waiting while it does a bunch of Java compilations. -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message