View Single Post
Old 04 September 2020, 17:43   #12
pipper
Registered User
 
Join Date: Jul 2017
Location: San Jose
Posts: 669
In my case I was lucky, vlink had already produced an output file. I used objdump to get a disassembly of the whole thing which gave me the offset plus the corresponding assembly. The offending offset will not directly show up as “line number” as the relocation is part of an instruction, but you’ll get close. Use this as reference in the original sources to lookup the actual offending instruction. Maybe there’s a more elegant way. But this worked for me.
pipper is offline  
 
Page generated in 0.04317 seconds with 11 queries