Types for objc_retain_xN / objc_release_xN in the libobjc type library should include their custom calling conventions
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- objective-c
- Domain
- reverse-engineering
Research direction
Start at bv.import_library_object and locate the libobjc type-library definitions for _objc_retain_xN and _objc_release_xN, then review the shared cache and Mach-O view workarounds described in the issue. Done means both views can import these symbols with the id signature and matching apple-arm64-objc-fast-arc-N calling convention without manual fixups.
Written by the indexing model from the issue text.
Description
Version and Platform (required):
- Binary Ninja Version: 5.3.9301-dev Ultimate, 855e811
- OS: macos
- OS Version: 26.3.1
- CPU Architecture: arm64
Bug Description:
>>> bv.import_library_object('_objc_release_x20')
<type: immutable:FunctionTypeClass 'void()'>
>>> bv.import_library_object('_objc_release_x20').calling_convention
Expected Behavior:
These functions should:
- Have the correct signature:
id _objc_release_x20(id). - Specify the custom calling convention (
apple-arm64-objc-fast-arc-20) to make explicit that the argument is not passed viax0.
Additional Information:
Both the shared cache and Mach-O views have to work around this at present by recognizing imports of these functions and manually fixing up the signature and calling convention.
- 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 ·