search for: 004004a0

...are. > The difference in the pastes, and my apologies for not explicitly pointing this out originally, is that the symbol addresses (see 'main') now seem to double-include the section address in their value. Notice how llvm-objdump gives address of 00800850 for main while objdump shows 004004a0. Note that before your changes llvm-objdump's output was aligned with that of normal objdump in this regard. > Eli > > (*) ELFObjectFile represents a relocatable file > It appears 100% of the/my problem is thinking ELFObjectFile was suitable for use on non-relocatable files such...

Hi, I would like to examine the implications you mention in more detail. (1) Symbol address According to the ELF standard, in a symbol table entry st_value means: "In relocatable files, st_value holds a section offset for a defined symbol. That is, st_value is an offset from the beginning of the section that st_shndx identifies." (*) Therefore, when queried about a symbol's

Hi all, I'm using the MC framework for a project, and while updating to latest trunk (r148672) encountered the following issue: It seems that SymbolRef::getAddress and SymbolRef::getFileOffset have been changed to add the symbol's offset to the offset of the containing section? This has the following implications: To get the /actual/ fileoffset, I now need to do: Symbol.getFileOffset()