Entry point offset should use segment virtual address
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 18
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
The entry point in the ELF file header (e_entry) is specified as a virtual address. However the logic that calculates TBF init_fn_offset compares it to the segment's physical address, resulting in an incorrect offset for ELF files where physical and virtual addresses differ.
The fix is trivial; PR incoming as I sort out my workflow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the logic that calculates the TBF init_fn_offset from the ELF entry point and segment addresses. Check the ELF header's e_entry handling against a segment whose physical and virtual addresses differ; the issue is complete when the offset is based on the segment virtual address and the differing-address case is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100