-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8250801: Add clhsdb "threadcontext" command #6925
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
|
sspitsyn
left a comment
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.
Chris,
I only have one question (inlined).
Other than that it looks good to me.
Thanks,
Serguei
src/jdk.hotspot.agent/share/classes/sun/jvm/hotspot/runtime/JavaThread.java
Outdated
Show resolved
Hide resolved
kevinjwalls
left a comment
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 useful to expose this info if we have it!
|
@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 43 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 |
|
/integrate |
|
Going to push as commit bdfa15d.
Your commit was automatically rebased without conflicts. |
|
@plummercj Pushed as commit bdfa15d. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
SA has the ability to fetch the thread's registers via the thread context. It would be nice to allow access to the registers from clhsdb. This plays in well with the enhancements being done to PointerFinder as part of JDK-8247514. Many of the register values will then be automatically displayed as symbols, Methods, Threads, stack offsets, nmethods, interpreter codelets, etc.
During some recent debugging I did I found it useful to dump a thread's registers in this manner. Although in this case I was inlining the code in the part of SA where I wanted to see the registers, having it as a clhsdb command would not only be useful to user, but also useful when debugging SA because it would serve as a code snippet to copy-n-paste where needed.
The syntax is:
Where -a displays all threads, and "id" is used to display a specific thread. This is the same argument syntax as some other commands that let you choose all threads or just one thread, such as the "thread" and "where" commands. -v just means more verbose output, whereas without it for the most part each register printed will just take up one line.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6925/head:pull/6925$ git checkout pull/6925Update a local copy of the PR:
$ git checkout pull/6925$ git pull https://git.openjdk.java.net/jdk pull/6925/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6925View PR using the GUI difftool:
$ git pr show -t 6925Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6925.diff