move function-name feature matching to insn scope
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
`function-name` features presently match at `file` scope which prevents detection like "function A calls function-name C then function-name D". Changing `function-name` features to match at the `insn` scope would also align with `api` matching.
Contributor guide
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
Trace how `function-name` features are matched at file scope, then compare that path with the existing `api` matching behavior. Update the matching scope so sequential calls such as function A calling function-name C and function-name D are detected; done means those cases match consistently at instruction scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100