4

The man page has this to say:

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.

The problem is that the values for STT_* and STB_* overlap. This is the declaration of those values in 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

I think I understand that the STB_* values are 'Bindings' and STT+* are 'Types', but since the values overlap, given a symbol table, how can I tell how to interpret this field?

Stephen
  • 2,613
  • 1
  • 24
  • 42

1 Answers1

5

how can I tell how to interpret this field?

Use ELF{32,64}_ST_BIND and ELF{32,64}_ST_TYPE macros to split st_info into its components.

Look in /usr/include/elf.h. You'll find something like:

/* How to extract and insert information held in the st_info field.  */
#define ELF32_ST_BIND(val) ...
#define ELF32_ST_TYPE(val) ...

... etc.
Employed Russian
  • 199,314
  • 34
  • 295
  • 362
  • 1
    Thanks for the answer, but I'm still confused. Assume the value of `st_info` is `2`. Does that mean `STB_WEAK` or does it mean `STT_FUNC`? – Stephen Jan 11 '18 at 06:42
  • Oh. I Think I get it. `#define ELF_ST_BIND(x) ((x) >> 4)` `#define ELF_ST_TYPE(x) (((unsigned int) x) & 0xf)` that means that if `st_info == 34` then it means `STB_WEAK` **and** `STT_FUNC` because `34 >> 4 == 2` and `34 & 0xff == 2`. Is that right? – Stephen Jan 11 '18 at 06:50
  • @Stephen Correct (but you should never need to think about it in terms of `34` -- just compare output of `readelf -Ws` with `STB_WEAK == ELF_ST_BIND(sym->st_info)`. – Employed Russian Jan 11 '18 at 15:41
  • Got it. I'm writing an ELF parser in python and this value was confusing. – Stephen Jan 12 '18 at 03:06