From 9acce7a6f326543c302ca0408213cf333f5f778a Mon Sep 17 00:00:00 2001 From: Ludvig Janiuk Date: Thu, 11 Apr 2024 10:33:19 +0000 Subject: [PATCH] 8329774: Break long lines in jdk/src/jdk.hotspot.agent/doc /transported_core.html Reviewed-by: kevinw --- .../doc/transported_core.html | 22 ++++++++++++++----- 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/src/jdk.hotspot.agent/doc/transported_core.html b/src/jdk.hotspot.agent/doc/transported_core.html index 272e9598757..7d8b2804d0a 100644 --- a/src/jdk.hotspot.agent/doc/transported_core.html +++ b/src/jdk.hotspot.agent/doc/transported_core.html @@ -87,18 +87,28 @@ 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. +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: +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: +

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:

@@ -117,13 +127,13 @@ jhsdb -J-Dsun.jvm.hotspot.debugger.windbg.symbolPath="%PATH%;srv*https://msdl.mi

For locating the user JNI libraries, SA uses DYLD_LIBRARY_PATH. It can contain more than one directory separated by a colon. DYLD_LIBRARY_PATH can also be - used for locating the JDK libraries, but it needs to specify the full path to the libraries. SA will - not automatically search subdirs such as lib/server as it does for JAVA_HOME. + used for locating the JDK libraries, but it needs to specify the full path to the libraries. SA + will not automatically search subdirs such as lib/server as it does for JAVA_HOME.

For locating the macOS libraries, SA uses SA_ALTROOT similar to the linux support, - except it does not use it to map all the subdirs. It just appends SA_ALTROOT to the + except it does not use it to map all the subdirs. It just prepends SA_ALTROOT to the full path of each macOS library. So if you specify SA_ALTROOT=/altroot, SA will prepend /altroot to the full path of each macOS library. Note however, due to JDK-8249779 , SA will not