如何解释精灵符号 table 部分的 st_info 字段
How to interpret the st_info field of elf symbol table section
man page 有话要说:
st_info This member specifies the symbol's type and binding
attributes:
STT_NOTYPE The symbol's type is not defined.
STT_OBJECT The symbol is associated with a data object.
STT_FUNC The symbol is associated with a function or other
executable code.
STT_SECTION The symbol is associated with a section. Symbol
table entries of this type exist primarily for
relocation and normally have STB_LOCAL bindings.
STT_FILE By convention, the symbol's name gives the name
of the source file associated with the object
file. A file symbol has STB_LOCAL bindings, its
section index is SHN_ABS, and it precedes the
other STB_LOCAL symbols of the file, if it is
present.
STT_LOPROC This value up to and including STT_HIPROC is
reserved for processor-specific semantics.
STT_HIPROC This value down to and including STT_LOPROC is
reserved for processor-specific semantics.
STB_LOCAL Local symbols are not visible outside the object
file containing their definition. Local symbols
of the same name may exist in multiple files
without interfering with each other.
STB_GLOBAL Global symbols are visible to all object files
being combined. One file's definition of a
global symbol will satisfy another file's
undefined reference to the same symbol.
STB_WEAK Weak symbols resemble global symbols, but their
definitions have lower precedence.
STB_LOPROC This value up to and including STB_HIPROC is
reserved for processor-specific semantics.
STB_HIPROC This value down to and including STB_LOPROC is
reserved for processor-specific semantics.
There are macros for packing and unpacking the
binding and type fields:
ELF32_ST_BIND(info) or ELF64_ST_BIND(info)
extract a binding from an st_info value.
ELF32_ST_TYPE(info) or ELF64_ST_TYPE(info)
extract a type from an st_info value.
ELF32_ST_INFO(bind, type) or ELF64_ST_INFO(bind,
type)
convert a binding and a type into an st_info
value.
问题是 STT_*
和 STB_*
的值重叠。这是 uapi/linux/elf.h:
中那些值的声明
#define STB_LOCAL 0
#define STB_GLOBAL 1
#define STB_WEAK 2
#define STT_NOTYPE 0
#define STT_OBJECT 1
#define STT_FUNC 2
#define STT_SECTION 3
#define STT_FILE 4
#define STT_COMMON 5
#define STT_TLS 6
我想我明白 STB_*
值是 'Bindings' 和 STT+*
是 'Types',但是由于值重叠,给定一个符号 table ,我怎么知道如何解释这个领域?
how can I tell how to interpret this field?
使用 ELF{32,64}_ST_BIND
和 ELF{32,64}_ST_TYPE
宏将 st_info
拆分为其组件。
查看/usr/include/elf.h
。你会发现类似:
/* How to extract and insert information held in the st_info field. */
#define ELF32_ST_BIND(val) ...
#define ELF32_ST_TYPE(val) ...
... etc.
man page 有话要说:
st_info This member specifies the symbol's type and binding
attributes:
STT_NOTYPE The symbol's type is not defined.
STT_OBJECT The symbol is associated with a data object.
STT_FUNC The symbol is associated with a function or other
executable code.
STT_SECTION The symbol is associated with a section. Symbol
table entries of this type exist primarily for
relocation and normally have STB_LOCAL bindings.
STT_FILE By convention, the symbol's name gives the name
of the source file associated with the object
file. A file symbol has STB_LOCAL bindings, its
section index is SHN_ABS, and it precedes the
other STB_LOCAL symbols of the file, if it is
present.
STT_LOPROC This value up to and including STT_HIPROC is
reserved for processor-specific semantics.
STT_HIPROC This value down to and including STT_LOPROC is
reserved for processor-specific semantics.
STB_LOCAL Local symbols are not visible outside the object
file containing their definition. Local symbols
of the same name may exist in multiple files
without interfering with each other.
STB_GLOBAL Global symbols are visible to all object files
being combined. One file's definition of a
global symbol will satisfy another file's
undefined reference to the same symbol.
STB_WEAK Weak symbols resemble global symbols, but their
definitions have lower precedence.
STB_LOPROC This value up to and including STB_HIPROC is
reserved for processor-specific semantics.
STB_HIPROC This value down to and including STB_LOPROC is
reserved for processor-specific semantics.
There are macros for packing and unpacking the
binding and type fields:
ELF32_ST_BIND(info) or ELF64_ST_BIND(info)
extract a binding from an st_info value.
ELF32_ST_TYPE(info) or ELF64_ST_TYPE(info)
extract a type from an st_info value.
ELF32_ST_INFO(bind, type) or ELF64_ST_INFO(bind,
type)
convert a binding and a type into an st_info
value.
问题是 STT_*
和 STB_*
的值重叠。这是 uapi/linux/elf.h:
#define STB_LOCAL 0
#define STB_GLOBAL 1
#define STB_WEAK 2
#define STT_NOTYPE 0
#define STT_OBJECT 1
#define STT_FUNC 2
#define STT_SECTION 3
#define STT_FILE 4
#define STT_COMMON 5
#define STT_TLS 6
我想我明白 STB_*
值是 'Bindings' 和 STT+*
是 'Types',但是由于值重叠,给定一个符号 table ,我怎么知道如何解释这个领域?
how can I tell how to interpret this field?
使用 ELF{32,64}_ST_BIND
和 ELF{32,64}_ST_TYPE
宏将 st_info
拆分为其组件。
查看/usr/include/elf.h
。你会发现类似:
/* How to extract and insert information held in the st_info field. */
#define ELF32_ST_BIND(val) ...
#define ELF32_ST_TYPE(val) ...
... etc.