-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8307480: Improve SA "transported core" documentation for windows #13849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👋 Welcome back cjplummer! A progress list of the required criteria for merging this PR into |
@plummercj The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
</p> | ||
|
||
<p> | ||
How you set these properties will depend on the SA tool being used. The following in an example of when launching the clhsdb tool: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo?: The following in an example of when launching...
=> The following is an example of launching...
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, or maybe "for launching". It's somewhat of a clumsy sentence, but the only fix for that I've come up with for that makes it kind of wordy: "The following example demonstrates how to set one of the properties when launching the clhsdb tool:"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Posted one comment about a potential typo.
Thanks,
Serguei
@plummercj This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 105 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@apavlyutkin Can you review this? |
Lgtm |
|
||
<p> | ||
You can also include user JNI libraries in <b>PATH</b>. | ||
If the windows libraries are not identical, then they may also need to be copied | ||
to the debugger machine and included in <b>PATH</b>. | ||
</p> | ||
|
||
<p> | ||
By default symbols are also located using <b>PATH</b>. 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 <b>sun.jvm.hotspot.debugger.windbg.imagePath</b> for the location of binaries, and use <b>sun.jvm.hotspot.debugger.windbg.symbolPath</b> for the location of symbols. <b>imagePath</b> defaults to <b>PATH</b> if not set, and <b>symbolPath</b> defaults to <b>imagePath</b>. The advantage of using these propeties is that you don't need to change your <b>PATH</b> setting, and they allow for binaries to be located separately from symbols. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is "also" needed here? The sentence makes more sense without it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "also" is in reference to the previous paragraph mentioning that binaries are located using PATH. In other words, PATH is by default used to locate binaries and also to locate symbols.
Looks good. |
Thanks for all the reviews! /integrate |
Going to push as commit 38838b3.
Your commit was automatically rebased without conflicts. |
@plummercj Pushed as commit 38838b3. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The SA document
transported_core.html
contains some tips on getting core files to work when debugging it on a machine other than the one that produced it. There are a few improvements that can be made based on information provided in JDK-8306437 and in the #13530 review (which was eventually pulled as not necessary).Updates to the document include the use of
sun.jvm.hotspot.debugger.windbg.imagePath
andsun.jvm.hotspot.debugger.windbg.symbolPath
properties, and adding "srv*https://msdl.microsoft.com/download/symbols
" to symbolPath.The rendered html file with these changes can be found here:
https://htmlpreview.github.io/?https://raw.githubusercontent.com/openjdk/jdk/75b10f672a461d3742c51db06ec2625605e45cf0/src/jdk.hotspot.agent/doc/transported_core.html
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/13849/head:pull/13849
$ git checkout pull/13849
Update a local copy of the PR:
$ git checkout pull/13849
$ git pull https://git.openjdk.org/jdk.git pull/13849/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 13849
View PR using the GUI difftool:
$ git pr show -t 13849
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13849.diff
Webrev
Link to Webrev Comment