From owner-freebsd-java@FreeBSD.ORG Thu Feb 3 21:24:45 2011 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id B7EDD106564A; Thu, 3 Feb 2011 21:24:45 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-java@freebsd.org Date: Thu, 3 Feb 2011 16:24:36 -0500 User-Agent: KMail/1.6.2 References: <201101261721.58069.jkim@FreeBSD.org> <201102021354.13333.jkim@FreeBSD.org> <1296756549.2298.3.camel@mjakubik-laptop> In-Reply-To: <1296756549.2298.3.camel@mjakubik-laptop> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201102031624.38310.jkim@FreeBSD.org> Cc: Pieter de Goeje , Mike Jakubik Subject: Re: [CFT] Update OpenJDK6 to b21 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2011 21:24:46 -0000 On Thursday 03 February 2011 01:09 pm, Mike Jakubik wrote: > On Wed, 2011-02-02 at 13:54 -0500, Jung-uk Kim wrote: > > Yeah, I actually fixed that. Some patches were missing in b20 > > ports. 'jstack -m' should work, too. :-) > > > > Thanks for testing! > > Compiled OK and working with my applications OK. The jstack -m > option you mention however produces the following results here: > > Attaching to process ID 84046, please wait... > Debugger attached successfully. > Server compiler detected. > JVM version is 19.0-b09 > sun.jvm.hotspot.debugger.DebuggerException: > sun.jvm.hotspot.debugger.DebuggerException: get_thread_regs failed > for a lwp > at sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal > $BsdDebuggerLocalWorkerThread.execute(BsdDebuggerLocal.java:152) > at > sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.getThreadIntegerRegis >terSet(BsdDebuggerLocal.java:466) at > sun.jvm.hotspot.debugger.bsd.BsdThread.getContext(BsdThread.java:65 >) at > sun.jvm.hotspot.runtime.bsd_amd64.BsdAMD64JavaThreadPDAccess.getCur >rentFrameGuess(BsdAMD64JavaThreadPDAccess.java:92) at > sun.jvm.hotspot.runtime.JavaThread.getCurrentFrameGuess(JavaThread. >java:256) at > sun.jvm.hotspot.runtime.JavaThread.getLastJavaVFrameDbg(JavaThread. >java:218) at > sun.jvm.hotspot.tools.PStack.initJFrameCache(PStack.java:208) at > sun.jvm.hotspot.tools.PStack.run(PStack.java:66) > at sun.jvm.hotspot.tools.PStack.run(PStack.java:53) > at sun.jvm.hotspot.tools.PStack.run(PStack.java:48) > at sun.jvm.hotspot.tools.JStack.run(JStack.java:60) > at sun.jvm.hotspot.tools.Tool.start(Tool.java:221) > at sun.jvm.hotspot.tools.JStack.main(JStack.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp >l.java:57) at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc >essorImpl.java:43) at > java.lang.reflect.Method.invoke(Method.java:616) > at sun.tools.jstack.JStack.runJStackTool(JStack.java:136) > at sun.tools.jstack.JStack.main(JStack.java:102) Yeah, I noticed that, too. It seems it's getting bogus thread IDs. It'll take some time for me to figure out why, though. :-( Jung-uk Kim