From owner-freebsd-java@FreeBSD.ORG Tue Dec 23 01:34:05 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 9F8A616A4CE for ; Tue, 23 Dec 2003 01:34:05 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AE8C43D31 for ; Tue, 23 Dec 2003 01:34:04 -0800 (PST) (envelope-from gwk@rahn-koltermann.de) Received: from [212.227.126.202] (helo=mrvnet.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AYivS-0001Gf-00 for freebsd-java@freebsd.org; Tue, 23 Dec 2003 10:34:02 +0100 Received: from [172.23.4.144] (helo=config17.kundenserver.de) by mrvnet.kundenserver.de with esmtp (Exim 3.35 #1) id 1AYivS-0000Em-00; Tue, 23 Dec 2003 10:34:02 +0100 Received: from www-data by config17.kundenserver.de with local (Exim 3.35 #1 (Debian)) id 1AYivS-0003r9-00; Tue, 23 Dec 2003 10:34:02 +0100 To: From: Message-Id: <27942123$10721709703fe807dae79210.60087527@config17.schlund.de> X-Binford: 6100 (more power) X-Originating-From: 27942123 X-Mailer: Webmail X-Routing: DE X-Received: from config17 by 213.148.149.130 with HTTP id 27942123 for freebsd-java@freebsd.org; Tue, 23 Dec 2003 10:32:03 +0100 Content-Type: text/plain; charset="iso-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Priority: 3 Date: Tue, 23 Dec 2003 10:32:03 +0100 X-Provags-ID: kundenserver.de abuse@kundenserver.de ident:@172.23.4.144 cc: gwk@rahn-koltermann.de Subject: 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 09:34:05 -0000 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.