Vector35 / Vector35/binaryninja-api
syscall instruction should reference the registers requried by the calling convention despite their values cannot be determined
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Related to: https://github.com/Vector35/binaryninja-api/issues/5129
For the above code, the analysis is unaware of the entry value of rax is 0x0 (this is a different bug, which is tracked by https://github.com/Vector35/binaryninja-api/issues/5129), but we should at least reference the rax (as well as others) registers in the syscall instruction, so that a UIDF can be set on it.
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
No file or test is named. Start by tracing syscall instruction analysis and the calling-convention register handling, then compare the behavior shown in the issue with related issue #5129. Done means the syscall instruction references the required registers even when their values cannot be determined, allowing UIDF to be set on them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100