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.
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>.soto one of the places where hotspot expects it.Also, we need to support calling out to proper
objdumpfor 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.