From owner-freebsd-java@FreeBSD.ORG  Sat Aug 23 09:38:39 2003
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
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 EDECF16A4C0
	for <java@freebsd.org>; Sat, 23 Aug 2003 09:38:39 -0700 (PDT)
Received: from 141.com (mail.141.com [65.168.139.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3851443FBD
	for <java@freebsd.org>; Sat, 23 Aug 2003 09:38:39 -0700 (PDT)
	(envelope-from arlankfo@141.com)
Date: Sat, 23 Aug 2003 10:42:32 -0600
Message-Id: <200308231042.AA1507524852@141.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: "Andrew Lankford" <arlankfo@141.com>
To: Daniel Eischen <eischen@vigrid.com>,
	Greg Lewis <glewis@misty.eyesbeyond.com>
X-Mailer: <IMail v8.02>
X-Declude-Sender: arlankfo@141.com [127.0.0.1]
X-Note: This E-mail was scanned for spam.
cc: java@freebsd.org
Subject: Re: jdk14 on -current
X-BeenThere: freebsd-java@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: arlankfo@141.com
List-Id: Porting Java to FreeBSD <freebsd-java.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-java>,
	<mailto:freebsd-java-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-java>
List-Post: <mailto:freebsd-java@freebsd.org>
List-Help: <mailto:freebsd-java-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-java>,
	<mailto:freebsd-java-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Aug 2003 16:38:40 -0000

Yeah, I noticed that problem while attempting to build jdk13
 with hotspot.  

BTW, I noticed that "setenv DEBUG_PROG gdb" doesn't work because
of the way DEBUG_PROG is used in the .java_wrapper script:

exec $DEBUG_PROG "$prog" "$vmopt" "$@"

>From a  quick look at the gdb manpage, I understand that gdb
isn't supposed to pass on the values of vmopt and $@ over to 
$prog.  Instead it just complains about them and exits.  I
 guess the other alternatives are to create a .gdbinit script
 on the fly or just do a 
" shell java YourProblematicJavaProggy " from gdb (neither of
 which help very much with the other problem I've encountered with running jdk13, oh vey ).

Andrew Lankford