RFR (S) 8217879: hs_err should print more instructions in hex dump

coleen.phillimore at oracle.com coleen.phillimore at oracle.com
Tue Jan 29 16:59:04 UTC 2019



On 1/29/19 5:34 AM, Aleksey Shipilev wrote:
> On 1/28/19 9:59 PM, coleen.phillimore at oracle.com wrote:
>> This seems fine.
>>
>> I was looking at this page:
>> https://onlinedisassembler.com/odaweb/
>>
>> What would be nice if the instructions looked like:
>>
>> Instructions: (pc=0x00007f911d0d6053, 0x00007f911d0d6143)
>>
>> and then just the hex dump, then I could cut/paste it into the window in that tool.  Or is there
>> another way?
> That's not unreasonable, but you need to have the PC marked in some way to see where it crashed.
> Right now I can read the hex dump and figure what are the bytes at PC, and cross-reference that with
> disassembly. Yes, that requires some hand work to remove the offsets when dumping to disassembler.

ok, too bad.
Coleen
>
> It also requires changing the os::print_hex_dump, which I am not very eager to do. In some sense,
> this should be the RFE against the disassembler itself, rather than our dumping code :)
>
> -Aleksey
>



More information about the hotspot-dev mailing list