Provide disassemblage for JIT methods #29
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.
The code needs more cleanup and stability before I will merge it.
The code is also very non-portable. I know it works for at least one of the JVMs I have installed but as this code contains some evil hacks like trying to guess C++ class memory layout to construct C++ classes from C code, it will probably break badly in sufficiently different environments. If someone has better ideas how to figure out the memory layout (maybe by accessing debug symbols?), please advice.
You need to put
hsdis-<arch>.so
to one of the places where hotspot expects it.Also, we need to support calling out to proper
objdump
for non-JITted DSOs.Another improvement would be to use a named pipe or a socket instead of this brittle write file / read file setup to transfer data from the target process to the agent loader.
Will fix #7 when ready.