Still prompts to launch binary when not compatible with system
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Version and Platform (required):
- Binary Ninja Version: 6.1.10552-dev
- OS: MacOS
- OS Version: 27
- CPU Architecture: M3 Pro
- Local or Remote Debugging: Local
Bug Description:
Hitting F6 or going through the right click menu will still prompt you to launch a binary, even if the debugger tab won't allow you (due to platform / arch compatibility issues).
Steps To Reproduce:
- Open a binary for a different platform or architecture
- Observe Debugger UI start is grayed out
- Hit F6, observe that launch prompt still pops up
Expected Behavior:
I should not be able to launch a binary at all when it is not compatible.
Screenshots/Video Recording:
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
Trace the F6 shortcut and right-click launch action, then compare their enablement with the debugger tab's platform and architecture compatibility check. Done means incompatible binaries cannot open the launch prompt through either path, while compatible binaries retain the existing launch behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100