Fix relocation addend sign extension on 32-bit platforms (#4846)

* Fix relocation addend sign extension on 32-bit platforms

When loading relocations on 32-bit platforms, the addend is read
as uint32 and zero-extended to uint64, which corrupts negative
addends. For example, -4 (0xFFFFFFFC) becomes 4294967292 instead
of remaining -4. Use int32 with sign extension to int64, matching
the Windows code path which already handles this correctly.
This commit is contained in:
Yi Liu 2026-03-09 10:09:28 +08:00 committed by GitHub
parent 539bebed9c
commit 163a91b05a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -3872,7 +3872,7 @@ load_relocation_section(const uint8 *buf, const uint8 *buf_end,
read_uint32(buf, buf_end, offset32);
relocation->relocation_offset = (uint64)offset32;
read_uint32(buf, buf_end, addend32);
relocation->relocation_addend = (uint64)addend32;
relocation->relocation_addend = (int64)(int32)addend32;
}
read_uint32(buf, buf_end, relocation->relocation_type);
read_uint32(buf, buf_end, symbol_index);