JDK-6313812 : SA: jstack on win-amd64 fails with No suitable match for type of address ...
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: windows_2003
  • CPU: x86
  • Submitted: 2005-08-20
  • Updated: 2019-08-15
  • Resolved: 2017-06-06
Related Reports
Relates :  
JDK-6794892 - sa-jdi tests fail with "Unable to deduce type of thread from address" on windows-x64 with server jvm
Description
On win amd64, many operations (eg jstack -F) fail like this:

Caused by: java.lang.RuntimeException: Unable to deduce type of thread from address 0x00000000004b7800 (expected type JavaThread, CompilerThread, LowMemoryDetectorThread, JvmtiAgentThread, JVMPIDaemonThread or SurrogateLockerThread)
	at sun.jvm.hotspot.runtime.Threads.createJavaThreadWrapper(Threads.java:125)
	at sun.jvm.hotspot.runtime.Threads.first(Threads.java:113)
	at sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:48)
	at sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:28)
	at sun.jvm.hotspot.tools.JStack.run(JStack.java:43)
	at sun.jvm.hotspot.tools.Tool.start(Tool.java:204)
	at sun.jvm.hotspot.tools.JStack.main(JStack.java:69)
	... 6 more
Caused by: sun.jvm.hotspot.types.WrongTypeException: No suitable match for type of address 0x00000000004b7800 (nearest symbol is jvm!??_7LowMemoryDetectorThread@@6B@)
	at sun.jvm.hotspot.runtime.VirtualConstructor.instantiateWrapperFor(VirtualConstructor.java:78)
Comments
This problem is not reproducible on JDK9. Ran jhsdb jstack --pid <> for about 100 times on windows amd64.
21-02-2017