Skip to content

LATX, fix: Preserve file offsets in process map records - #491

Open
yzewei wants to merge 1 commit into
lat-opensource:masterfrom
yzewei:fix-latx-process-map-offset
Open

yzewei wants to merge 1 commit into
lat-opensource:masterfrom
yzewei:fix-latx-process-map-offset

Conversation

@yzewei

@yzewei yzewei commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

The file offsets parsed by read_self_maps() are not stored in MapInfo, causing file-backed mappings in the guest's /proc/self/maps to report zero offsets.

libffi uses these offsets to locate its static trampoline code. Preserve the parsed offsets to prevent incorrect code mappings and crashes when callbacks are invoked.

The issue was discovered in NumPy's Numba JIT test.

The file offsets parsed by read_self_maps() are not stored in MapInfo,
causing file-backed mappings in the guest's /proc/self/maps to report
zero offsets.

libffi uses these offsets to locate its static trampoline code.
Preserve the parsed offsets to prevent incorrect code mappings and
crashes when callbacks are invoked.

The issue was discovered in NumPy's Numba JIT test.

Signed-off-by: Zewei Yang <yangzewei@loongson.cn>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant