Override call type dialog should show current call type at first time open
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- reverse-engineering
Research direction
Reproduce the issue by opening the call-type override dialog for a call whose inferred signature is visible in linear view. Trace the dialog's initial value and compare it with the call type Binary Ninja has already detected. Done means the first-open value reflects the detected signature instead of the generic void calltarget() placeholder.
Written by the indexing model from the issue text.
Description
Version and Platform (required):
- Binary Ninja Version: 3.6.4719-dev, dec72a07
- OS: macos
- OS Version: 14.2
- CPU Architecture: arm64
Bug Description:
Let's say there is a function call in linear view like this:
job->callback(job, config, job->field_10)
When I try to override call type for this call, dialog show me this as default call type: void calltarget(). But obviously there is different call type detected by BN. Instead of void calltarget(), BN should show me current call type which is something like this: void (* callback)(struct my_job*, struct config*, int64_t).
If BN do so and it predicts it correctly, I can easily copy that and set structure member type to that.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
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.
More from Vector35/binaryninja-api
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8540 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Vector35/binaryninja-api#8503 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8446 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8444 ·
All issues in Vector35/binaryninja-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·