PC-relative read in indirect jump was not modified during relocation

[mxz297]

Reported by Victor van der Veen.

When relocating the following function
000000000089c550 <uv__malloc>:
89c550: 55 push %rbp
89c551: 48 89 e5 mov %rsp,%rbp
89c554: 5d pop %rbp
89c555: ff 25 55 5d 41 00 jmpq *0x415d55(%rip) # cb22b0 <uv__allocator.0>

the indirect jump at "89c555" contains a PC-relative memory reference and the address of the memory access should be compensated after relocation, which does not happen.

I am able to reproduce this bug on current master with the provided mutator and mutatee.

[mxz297]

The indirect jump is an indirect tail call and should be treated as an indirect call during relocation. The current code only checks information from instructionAPI to determine whether an instruction is call or not, so our current code would wrongly claim that this indirect jump is not an indirect call.

I add code to check whether the relocation block ends with an indirect tail call. Victor has confirmed that the my fix solves his issue.