When HotSpot needs to print machine code (e.g. when printing a hs-err log) it tries to load the hsdis disassembler. If that fails because hsdis is absent, a hex dump is printed. Unfortunately that hex dump is hard to use. It is in an unfamiliar format, and it's very hard to disassemble it.
If the hex dump produced by HotSpot were in a format compatible with the platform assembler, standard tools (as and objdump) could be used to convert the hex dump to readable assembly code.
We should change the output of the HotSpot hex dump in the following ways:
- Replace the ";" with a platform-defined comment character
- Replace the address with a comment
- Replace the hex format with a line parseable by an assembler, in a platform-defined format
- A few other minor things to make the dump compatible with the platform assembler.
With these changes it would be easy for a maintenance programmer to convert hs-err crash files into readable assembly code, even without hsdis being present at runtime.
If the hex dump produced by HotSpot were in a format compatible with the platform assembler, standard tools (as and objdump) could be used to convert the hex dump to readable assembly code.
We should change the output of the HotSpot hex dump in the following ways:
- Replace the ";" with a platform-defined comment character
- Replace the address with a comment
- Replace the hex format with a line parseable by an assembler, in a platform-defined format
- A few other minor things to make the dump compatible with the platform assembler.
With these changes it would be easy for a maintenance programmer to convert hs-err crash files into readable assembly code, even without hsdis being present at runtime.