-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8294160: misc crash dump improvements #10387
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 dlong! A progress list of the required criteria for merging this PR into |
@dean-long 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
|
/cc hotspot-runtime |
@dean-long |
@dean-long |
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.
I'm not familiar with all the aspects of this in enough detail so just a couple of observational comments.
@@ -348,7 +354,7 @@ void os::print_tos_pc(outputStream *st, const void *context) { | |||
// Note: it may be unsafe to inspect memory near pc. For example, pc may | |||
// point to garbage if entry point in an nmethod is corrupted. Leave | |||
// this at the end, and hope for the best. | |||
address pc = os::Posix::ucontext_get_pc(uc); | |||
address pc = os::fetch_frame_from_context(uc).pc(); |
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.
What is the difference between ucontext_get_pc(uc)
and getting the pc from the frame from the uc? How many pc's can a ucontext have?
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 former returns the PC where the crash happened, which could be in unreadable memory. Blindly inspecting that memory will cause error reporting to crash. The latter returns the PC of a frame constructed from the context, and possibly adjusted to reflect where the caller was when it made the bad call, which is more useful for getting stack backtraces and less likely to crash error reporting. When error reporting crashes we recover, but we don't get the information it was dumping when it crashed.
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.
Okay seems quite reasonable. Thanks.
@dean-long 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 87 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 |
Thanks David. |
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.
Thanks Vladimir. |
/integrate |
Going to push as commit 6f8f28e.
Your commit was automatically rebased without conflicts. |
@dean-long Pushed as commit 6f8f28e. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Try to recover and output meaningful information in more situations, such as:
When calling a bad address, we usually don't get a meaningful stack backtrace, but in many situations we can if we know where to find the caller information.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10387/head:pull/10387
$ git checkout pull/10387
Update a local copy of the PR:
$ git checkout pull/10387
$ git pull https://git.openjdk.org/jdk pull/10387/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10387
View PR using the GUI difftool:
$ git pr show -t 10387
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10387.diff