Vector35 / Vector35/binaryninja-api
Log address matching too eager
Open
Nobody has claimed this yet.
Component: UI
Effort: Low
Impact: Low
UI: Logs
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
We should only match something like /(?=\s*)((0x)?[0-9]+)(?=\s*)/g
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 in the issue. Start by locating the logging code that performs address matching, then compare its behavior with the proposed pattern. Done means ordinary text is not matched as an address while the intended decimal and optional-0x forms still are.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100