Reports loaded libraries in crashtracking reports#11000
Open
Reports loaded libraries in crashtracking reports#11000
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Does This Do
Hotspot crashlogs have a Dynamic Libraries section, this PR reports it in the error event.
There are some differences between OSes, on Linux the JVM uses the procfs to write that section; on BSD, the JVM uses an internal track of loaded libraries, as such this data is named
dynamic_librariesMotivation
The dynamic libraries provide useful information to the actual path of the libraries, in particular the name of each lib can hint at the expected version of the native lib.
Additional Notes