What is the feature you'd like to have?
When a DLL has relocations for vtable members, there are no xrefs created to implementation functions in the binary. The vtable data shows as int32_t (* f)(struct Virtual* this) = 0x0 and no xref to the existing implementation in the analysis is made.
Is your feature request related to a problem?
The user wants to follow a vtable in a relocatable binary (dll).
Are any alternative solutions acceptable?
Maybe we could modify the data under the vtable to point to the correct address? We do this in some other places for relocations, but not here. Not sure if that is intentional.
Otherwise, there is no easy way to follow this information without writing another parser for the relocations and doing the annotation manually.
Additional Information:
Reported by mochaa on pubslack. Sample binary: vtbl.zip at 0x1800bfbd8
What is the feature you'd like to have?
When a DLL has relocations for vtable members, there are no xrefs created to implementation functions in the binary. The vtable data shows as
int32_t (* f)(struct Virtual* this) = 0x0and no xref to the existing implementation in the analysis is made.Is your feature request related to a problem?
The user wants to follow a vtable in a relocatable binary (dll).
Are any alternative solutions acceptable?
Maybe we could modify the data under the vtable to point to the correct address? We do this in some other places for relocations, but not here. Not sure if that is intentional.
Otherwise, there is no easy way to follow this information without writing another parser for the relocations and doing the annotation manually.
Additional Information:
Reported by mochaa on pubslack. Sample binary: vtbl.zip at 0x1800bfbd8