[Nasm-bugs] [Bug 3392347] macho32 format bug: LC_SEGMENT command 0 filesize field greater than vmsize field

no-reply at bugzilla-nasm.gorcunov.org no-reply at bugzilla-nasm.gorcunov.org
Thu Apr 28 12:07:39 PDT 2016


http://bugzilla.nasm.us/show_bug.cgi?id=3392347

zenith432 at users.sourceforge.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zenith432 at users.sourceforge
                   |                            |.net

--- Comment #1 from zenith432 at users.sourceforge.net ---
Why do you consider this a bug?

The text section begins at file offset 0x0F4, ends 0x12D (size 0x39), has
vmaddress 0.
The data section begins at file offset 0x130, ends 0x134 (size 4), has
vmaddress 0x39.

So the mismatch is due to a 3-byte padding between text and data sections,
maybe due to alignment in the file, an alignment which is not in the vm layout.

The Mac OS X ABI Mach-O File Format Reference published by Apple does not
prohibit this.  It may be awkward, but do you have problems linking the object
file?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.


More information about the Nasm-bugs mailing list