Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via JDK Bug System by Vladimir Kozlov, 1 year ago
Doesn't appear to be a HotSpot VM (could not find symbol "gHotSpotVMTypes" in remote process)
via nabble.com by Unknown author, 1 year ago
Doesn't appear to be a HotSpot VM (could not find symbol "gHotSpotVMTypes" in remote process)
via marc.info by Unknown author, 1 year ago
Doesn't appear to be a HotSpot VM (could not find symbol "gHotSpotVMTypes" in remote process)
via GitHub by shenwenxin
, 1 month ago
Doesn't appear to be a HotSpot VM (could not find symbol "gHotSpotVMTypes" in remote process)
via GitHub by oldratlee
, 2 months ago
Doesn't appear to be a HotSpot VM (could not find symbol "gHotSpotVMTypes" in remote process)
sun.jvm.hotspot.debugger.DebuggerException: Doesn't appear to be a HotSpot VM (could not find symbol "gHotSpotVMTypes" in remote process) at sun.jvm.hotspot.HotSpotAgent.setupVM(HotSpotAgent.java:412) at sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:305) at sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:156) at sun.jvm.hotspot.CLHSDB.attachDebugger(CLHSDB.java:202) at sun.jvm.hotspot.CLHSDB.access$400(CLHSDB.java:33) at sun.jvm.hotspot.CLHSDB$2.attach(CLHSDB.java:78) at sun.jvm.hotspot.CommandProcessor$2.doit(CommandProcessor.java:410) at sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:1951) at sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:1921) at sun.jvm.hotspot.CommandProcessor.run(CommandProcessor.java:1801) at sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:99) at sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:40)