PIT failures in jmap: Unable to deduce type of thread
Mattias Tobiasson
mattias.tobiasson at oracle.com
Fri Nov 14 09:43:35 UTC 2014
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 in, but mayvbe it was not?
Mattias
----- Original Message -----
From: mattias.tobiasson at oracle.com
To: serviceability-dev at openjdk.java.net
Cc: dmitry.fazunenko at oracle.com, albert.noll at 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 not 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 0x00007f93e419c800 (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(DeadlockDetector.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.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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(BsdDebuggerLocal.java:513)
at sun.jvm.hotspot.debugger.DebuggerBase.readAddressValue(DebuggerBase.java:462)
at sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.readAddress(BsdDebuggerLocal.java:448)
at sun.jvm.hotspot.debugger.bsd.BsdAddress.getAddressAt(BsdAddress.java:74)
at sun.jvm.hotspot.runtime.InstanceConstructor.newWrongTypeException(InstanceConstructor.java:52)
at sun.jvm.hotspot.runtime.VirtualConstructor.instantiateWrapperFor(VirtualConstructor.java:80)
at sun.jvm.hotspot.runtime.Threads.createJavaThreadWrapper(Threads.java:163)
More information about the serviceability-dev
mailing list