From owner-freebsd-java@FreeBSD.ORG Tue Dec 23 05:37:11 2003 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 9319F16A4CE for ; Tue, 23 Dec 2003 05:37:11 -0800 (PST) Received: from phantom.cris.net (phantom.cris.net [212.110.130.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A38143D39 for ; Tue, 23 Dec 2003 05:37:08 -0800 (PST) (envelope-from ml@FreeBSD.org.ua) Received: from phantom.cris.net (ml@localhost [127.0.0.1]) by phantom.cris.net (8.12.10/8.12.10) with ESMTP id hBNDb5l7006740; Tue, 23 Dec 2003 15:37:06 +0200 (EET) (envelope-from ml@FreeBSD.org.ua) Received: (from ml@localhost) by phantom.cris.net (8.12.10/8.12.10/Submit) id hBNDb3fO006739; Tue, 23 Dec 2003 15:37:03 +0200 (EET) (envelope-from ml) Date: Tue, 23 Dec 2003 15:37:02 +0200 From: Alexey Zelkin To: gwk@rahn-koltermann.de Message-ID: <20031223133702.GA6724@phantom.cris.net> References: <27942123$10721709703fe807dae79210.60087527@config17.schlund.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27942123$10721709703fe807dae79210.60087527@config17.schlund.de> X-Operating-System: FreeBSD 4.9-STABLE i386 User-Agent: Mutt/1.5.5.1i cc: freebsd-java@freebsd.org Subject: Re: java in free(): warning: junk pointer, too high to make sense 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, 23 Dec 2003 13:37:11 -0000 hi, Never seen this before. Can you please unset MALLOC_OPTIONS, get core dump and send me backtrace output ? On Tue, Dec 23, 2003 at 10:32:03AM +0100, gwk@rahn-koltermann.de wrote: > > Hi, > > when I ran Eclipse 3.0M5 on -current, I just got > "java in free(): warning: junk pointer, too high to make sense" > repeatedly. > > Both Eclipse and the JDK that I use, 1.4.2p5, were compiled on > FreeBSD 5.1R. I never noticed this error on 5.1R, but maybe the > malloc debugging options were not enabled by default there. On > -current I even have to set MALLOC_OPTIONS=a otherwise this warning > will be fatal and abort the program. > > Now that I try to reproduce and catch a core file, the problem > doesn't trigger any more :-(( > > Has anybody else seen this warning? Is it a problem in the native > part of Eclipse or in the JDK? > > -- > Regards, > Georg. > _______________________________________________ > freebsd-java@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-java > To unsubscribe, send any mail to "freebsd-java-unsubscribe@freebsd.org"