diff --git a/src/jdk.hotspot.agent/doc/transported_core.html b/src/jdk.hotspot.agent/doc/transported_core.html index 121cba6573f..272e9598757 100644 --- a/src/jdk.hotspot.agent/doc/transported_core.html +++ b/src/jdk.hotspot.agent/doc/transported_core.html @@ -76,9 +76,9 @@ installed on the debugger machine. is setup:

-

+ set PATH=%JAVA_HOME%\bin;%JAVA_HOME%\bin\server;%PATH% -

+

You can also include user JNI libraries in PATH. @@ -86,6 +86,25 @@ If the windows libraries are not identical, then they may also need to be copied to the debugger machine and included in PATH.

+

+By default symbols are also located using PATH. However, there are also Java properties that can be used to specify both the location of the binaries, and also separately the location of symbols. Use sun.jvm.hotspot.debugger.windbg.imagePath for the location of binaries, and use sun.jvm.hotspot.debugger.windbg.symbolPath for the location of symbols. imagePath defaults to PATH if not set, and symbolPath defaults to imagePath. The advantage of using these propeties is that you don't need to change your PATH setting, and they allow for binaries to be located separately from symbols. +

+ +

+How you set these properties will depend on the SA tool being used. The following example demonstrates how to set one of the properties when launching the clhsdb tool: +

+ + +jhsdb -J-Dsun.jvm.hotspot.debugger.windbg.imagePath="%PATH%;D:\SomePath" clhsdb + + +

If you are not seeing symbols for Windows libraries, try setting sun.jvm.hotspot.debugger.windbg.symbolPath to include "srv*https://msdl.microsoft.com/download/symbols". Also include PATH so SA will still find your JVM and JNI symbols. For example: +

+ + +jhsdb -J-Dsun.jvm.hotspot.debugger.windbg.symbolPath="%PATH%;srv*https://msdl.microsoft.com/download/symbol" clhsdb + +

Using transported core dumps on macOS

SA normally uses the path to the specified java executable to locate the JDK libraries. It will look