Vector35 / Vector35/binaryninja-api

[ObjC] Method implementations should have some way to see potential callers

Open
#7,091 0 comments 2 reactions 1 assignee View on GitHub

@bdash is already working on this.

Since Jul 14, 2025.

Component: Objective-C Workflow Effort: Low Impact: Medium
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

What is the feature you'd like to have?
Objective-C method implementations should have some way to show potential callers (via objc_msgSend or similar). This might be as simple as adding cross-references.

When using "Resolve Dynamic Dispatch Calls" the method implementation naturally has cross-references to any callers that were rewritten to it.

Are any alternative solutions acceptable?
The current workaround to see potential callers of a method implementation is to use cross-references to navigate from the implementation to its selector, then select the selector in the linear / graph view. That will show the selector's cross references which will include all objc_msgSend / objc_msgSendSuper2 callers that reference it.

Additional Information:
"Resolve Dynamic Dispatch Calls" is no longer on by default. It was disabled because it always resolves selectors to the first class that happens to implement the selector. This is often entirely wrong for common selector names.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.