[prev in list] [next in list] [prev in thread] [next in thread]
List: openjdk-serviceability-dev
Subject: Re: PIT failures in jmap: Unable to deduce type of thread
From: Mattias Tobiasson <mattias.tobiasson () oracle ! com>
Date: 2014-11-14 9:43:35
Message-ID: fa0c101d-cebc-43a7-a53a-1a317135a3cd () default
[Download RAW message or body]
Or maybe the PIT was just started before the fix for JDK-8062735 was in?
Pit started on november 7, and bug was closed on november 6. It should be i=
n, but mayvbe it was not?
Mattias
----- Original Message -----
From: mattias.tobiasson@oracle.com
To: serviceability-dev@openjdk.java.net
Cc: dmitry.fazunenko@oracle.com, albert.noll@oracle.com
Sent: Friday, November 14, 2014 10:39:07 AM GMT +01:00 Amsterdam / Berlin /=
Bern / Rome / Stockholm / Vienna
Subject: PIT failures in jmap: Unable to deduce type of thread
Hi,
Many tmtools/jmap and tmtools/jstack tests fails in PIT.
Below is a typical stack trace.
My guess is that this is the same thing as last week about serviceability n=
ot recognizing a new compiler thread.
https://bugs.openjdk.java.net/browse/JDK-8062735
Tests only fails on Mac.
Does anyone know what the problem is?
Thanks,
Mattias
java.lang.RuntimeException: Unable to deduce type of thread from address 0x=
00007f93e419c800 (expected type JavaThread, CompilerThread, ServiceThread, =
JvmtiAgentThread, SurrogateLockerThread, or CodeCacheSweeperThread)
at sun.jvm.hotspot.runtime.Threads.createJavaThreadWrapper(Threads.java:167=
)
at sun.jvm.hotspot.runtime.Threads.first(Threads.java:151)
at sun.jvm.hotspot.runtime.DeadlockDetector.createThreadTable(DeadlockDetec=
tor.java:149)
at sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:56)
at sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:39)
at sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:62)
at sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:45)
at sun.jvm.hotspot.tools.JStack.run(JStack.java:66)
at sun.jvm.hotspot.tools.Tool.startInternal(Tool.java:260)
at sun.jvm.hotspot.tools.Tool.start(Tool.java:223)
at sun.jvm.hotspot.tools.Tool.execute(Tool.java:118)
at sun.jvm.hotspot.tools.JStack.main(JStack.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav=
a:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor=
Impl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.tools.jstack.JStack.runJStackTool(JStack.java:140)
at sun.tools.jstack.JStack.main(JStack.java:106)
Caused by: sun.jvm.hotspot.debugger.UnmappedAddressException: 7f93e419c800
at sun.jvm.hotspot.debugger.PageCache.checkPage(PageCache.java:208)
at sun.jvm.hotspot.debugger.PageCache.getData(PageCache.java:63)
at sun.jvm.hotspot.debugger.DebuggerBase.readBytes(DebuggerBase.java:225)
at sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.readCInteger(BsdDebugger=
Local.java:513)
at sun.jvm.hotspot.debugger.DebuggerBase.readAddressValue(DebuggerBase.ja=
va:462)
at sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.readAddress(BsdDebuggerL=
ocal.java:448)
at sun.jvm.hotspot.debugger.bsd.BsdAddress.getAddressAt(BsdAddress.java:7=
4)
at sun.jvm.hotspot.runtime.InstanceConstructor.newWrongTypeException(Inst=
anceConstructor.java:52)
at sun.jvm.hotspot.runtime.VirtualConstructor.instantiateWrapperFor(Virtu=
alConstructor.java:80)
at sun.jvm.hotspot.runtime.Threads.createJavaThreadWrapper(Threads.java:1=
63)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic