Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Feb 2011 16:24:36 -0500
From:      Jung-uk Kim <jkim@FreeBSD.org>
To:        freebsd-java@freebsd.org
Cc:        Pieter de Goeje <pieter@degoeje.nl>, Mike Jakubik <mike.jakubik@intertainservices.com>
Subject:   Re: [CFT] Update OpenJDK6 to b21
Message-ID:  <201102031624.38310.jkim@FreeBSD.org>
In-Reply-To: <1296756549.2298.3.camel@mjakubik-laptop>
References:  <201101261721.58069.jkim@FreeBSD.org> <201102021354.13333.jkim@FreeBSD.org> <1296756549.2298.3.camel@mjakubik-laptop>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201102031624.38310.jkim>