Skip to content

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

Closed

Conversation

plummercj
Copy link
Contributor

@plummercj plummercj commented May 5, 2023

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 and sun.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

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8307480: Improve SA "transported core" documentation for windows

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

@bridgekeeper
Copy link

bridgekeeper bot commented May 5, 2023

👋 Welcome back cjplummer! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk openjdk bot changed the title 8307480 8307480: Improve SA "transported core" documentation for windows May 5, 2023
@openjdk openjdk bot added the rfr Pull request is ready for review label May 6, 2023
@openjdk
Copy link

openjdk bot commented May 6, 2023

@plummercj The following label will be automatically applied to this pull request:

  • serviceability

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.

@openjdk openjdk bot added the serviceability serviceability-dev@openjdk.org label May 6, 2023
@mlbridge
Copy link

mlbridge bot commented May 6, 2023

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:
Copy link
Contributor

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....

Copy link
Contributor Author

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:"

Copy link
Contributor

@sspitsyn sspitsyn left a 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

@openjdk
Copy link

openjdk bot commented May 6, 2023

@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:

8307480: Improve SA "transported core" documentation for windows

Reviewed-by: sspitsyn, kevinw, poonam

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 master branch:

  • 2bf7ac5: 8297657: name demangling intermittently fails
  • d20034b: 8307058: Implementation of Generational ZGC
  • 0cbfbc4: 8307813: [JVMCI] Export markWord::lock_mask_in_place to JVMCI compilers.
  • ba9714d: 8307610: Linker::nativeLinker should not be restricted (mainline)
  • ecc1d85: 8307869: Remove unnecessary log statements from arm32 fastlocking code
  • 08fa269: 8307349: Support xlc17 clang toolchain on AIX
  • 8ac7186: 8305416: runtime/Thread/TestAlwaysPreTouchStacks.java failed with "Did not find expected NMT output"
  • 984fbbb: 8307810: Consistently use LockingMode instead of UseHeavyMonitors
  • 39f4e4d: 8307758: RISC-V: Improve bit test code introduced by JDK-8291555
  • 3cb606e: 8306965: osThread allocation failures should not abort the VM
  • ... and 95 more: https://git.openjdk.org/jdk/compare/1b143ba78712e7ac98ca9873c50989b3fba07394...master

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 6, 2023
@plummercj
Copy link
Contributor Author

@apavlyutkin Can you review this?

@apavlyutkin
Copy link
Contributor

Lgtm

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label May 9, 2023
@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 9, 2023
@openjdk openjdk bot added ready Pull request is ready to be integrated and removed ready Pull request is ready to be integrated labels May 10, 2023

<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.
Copy link
Member

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.

Copy link
Contributor Author

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.

@poonamparhar
Copy link
Member

Looks good.

@plummercj
Copy link
Contributor Author

Thanks for all the reviews!

/integrate

@openjdk
Copy link

openjdk bot commented May 12, 2023

Going to push as commit 38838b3.
Since your change was applied there have been 141 commits pushed to the master branch:

  • 9842ff4: 8306607: Apply 80-column output to javac supported version output
  • d809823: 8306471: Add virtual threads support to JDWP ThreadReference.Stop and JDI ThreadReference.stop()
  • 4441a23: 6714245: [Col] Collator - Faster Comparison for identical strings.
  • a284920: 8168469: Memory leak in JceSecurity
  • 7455bb2: 8308015: Syntax of "import static" is incorrect in com.sun.source.tree.ImportTree.java
  • 6ebea89: 8307911: javadoc for MemorySegment::reinterpret has duplicate restricted method paragraph
  • 3c68c35: 8307535: java.util.logging.Handlers should be more VirtualThread friendly
  • 9fa8b9a: 8307409: Refactor usage examples to use @snippet in the java.nio packages
  • e512a20: 8306541: Refactor collection set candidate handling to prepare for JDK-8140326
  • 4b0f421: 8307855: update for deprecated sprintf for src/utils
  • ... and 131 more: https://git.openjdk.org/jdk/compare/1b143ba78712e7ac98ca9873c50989b3fba07394...master

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label May 12, 2023
@openjdk openjdk bot closed this May 12, 2023
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels May 12, 2023
@openjdk
Copy link

openjdk bot commented May 12, 2023

@plummercj Pushed as commit 38838b3.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integrated Pull request has been integrated serviceability serviceability-dev@openjdk.org
Development

Successfully merging this pull request may close these issues.

5 participants