Hi Jiawei,
Thanks for fixing this issue! I didn't subscribe our mailing list so I add a "Re:" in the title and expect this mail could append to our thread of discussion.
Seems to me this patch has not yet been committed, so we have time to discuss.
My question is simple:
There seem to be two [1] [2] `memory_error_func` used in `print_insn_riscv`. Seems the first one is an opcode pre-fetch and the other one is the real one. So, should the other one be fixed as well? ;-)
[1] https://github.com/bminor/binutils-gdb/blob/9e4b2a6697006f9ff39bce13edd640330e208c9f/opcodes/riscv-dis.c#L1061 <https://github.com/bminor/binutils-gdb/blob/9e4b2a6697006f9ff39bce13edd640330e208c9f/opcodes/riscv-dis.c#L1061 >
[2] https://github.com/bminor/binutils-gdb/blob/9e4b2a6697006f9ff39bce13edd640330e208c9f/opcodes/riscv-dis.c#L1073 <https://github.com/bminor/binutils-gdb/blob/9e4b2a6697006f9ff39bce13edd640330e208c9f/opcodes/riscv-dis.c#L1073 >
Best Regards,
Xiaolin