RelView: segments have no file backing, so no functions are created
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Split out of #17. With the len() crash fixed, RelView creates its segment but still ends up with 0 functions:
Analysis error: Attempting to add function not backed by file: 0x37
init() calls add_auto_segment(addr, size, 0, 0, ...) — data length 0, so the segment is not backed by the file and Binary Ninja will not place functions in it.
The .rel format is textual, so the code bytes come from T records rather than a contiguous file region. Backing the segment with the file directly (add_auto_segment(addr, size, 0, size, ...)) is not a fix: self.write() then modifies the parent view, and the next load attempt dies with UnicodeDecodeError when re-parsing what is supposed to be text.
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 in the RelView init() implementation and trace how add_auto_segment() and self.write() interact with the parent view. Determine how T-record code bytes can back the segment without modifying the textual .rel source, then verify that functions are created and a subsequent load does not raise UnicodeDecodeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100