Anonymous user
COFF: Difference between revisions
→String Table: Mention alternate section name encoding
| [unchecked revision] | [unchecked revision] |
(→External Links: Add link to official Microsoft COFF spec) |
(→String Table: Mention alternate section name encoding) |
||
Line 328:
===String Table===
The String
The String
<pre>
String Table Offset = File Header.f_symptr + File Header.f_nsyms * sizeof( Symbol Table Entry )
Line 336:
</pre>
The first four bytes of the
The Section
<source lang="c">
{
Line 353:
</source>
If the name is eight characters or fewer, then the field "zeroes" will be non-zero, and "name" should be
If the name is more than eight characters, the "zeroes" field (the first four bytes of "name") will be zero. In this case the "offset" field should be used as an offset value into the String table to locate the Symbol or Section name.
NOTE: Some tools (like GCC) use a different format for the section name field. Instead of the first four bytes being zero and the last four being an offset into the string table (as described just above), the first byte is a `/`, and the rest are the decimal digits of the offset within the string table where the section name may be found. For example, a section named ".name_thats_too_long" will have "/4" stored in its section name field, assuming this is the first string stored in the string table.
==Example==
| |||