Trying to analize JVM coredumps on Windows I always see 'Doesn't appear to be a HotSpot VM (could not find symbol "gHotSpotVMTypes" in remote process)' message.

Typically we get from a customer a coredump and JVM version. I deploy corresponding JDK image to my workspace along with PDB-files and use it to parse coredump. I tried to play with PATH and JAVA_HOME enviroinment variable but didn't succeed.

The only known workaround to me is to deploy JVM image at the exactly same path as crashed instance was. Probably that is because Windows coredumps use absolute paths.

I hardcoded image & symbol path in WindbgDebuggerLocal with desired values but even that did not help until I prepended symbol path with srv*https://msdl.microsoft.com/download/symbols pointing WinDbg where to search for Windows symbol tables.

The idea of proposed fix is to use executableName as a hint in the case when paths are not specified by

sun.jvm.hotspot.debugger.windbg.imagePath
sun.jvm.hotspot.debugger.windbg.symbolPath

Now in this case image & symbol paths are initialized with only content of PATH environment variable. I would suggest to prepend this value with

[executable_folder];[executable_folder]\server

for image path and

srv*https://msdl.microsoft.com/download/symbols;[executable_folder];[executable_folder]\server

for symbol path