F3 (Find Next) shortcut does not work, possibly due to conflict with Add Hardware Breakpoint key binding
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- cpp
- Domain
- desktop, reverse-engineering
Research direction
Start in the key bindings settings and compare the F3 entries for Find Next and Add Hardware Breakpoint; use Edit -> Find Next as the working behavior to trace. Done means F3 advances an existing search to its next match without a conflicting F3 binding.
Written by the indexing model from the issue text.
Description
Version and Platform (required):
- Binary Ninja Version: 6.0.10474-dev Ultimate (c9ea4d90)
- Edition: Ultimate
- OS: Windows 11 Pro
- OS Version: 10.0.26200 (Build 26200)
- CPU Architecture: x64 (AMD64 Family 25 Model 97, running under QEMU/Proxmox virtualization)
Bug Description:
Pressing the F3 keyboard shortcut for Find Next does not do anything. However, using Menu -> Edit -> Find Next works correctly. Checking the key bindings shows that F3 is assigned to both "Find Next" and "Add Hardware Breakpoint", which appears to be causing the conflict preventing Find Next from triggering via the shortcut.
Steps To Reproduce:
- Open a binary in Binary Ninja
- Perform a search (e.g. via Find) so that Find Next has a target to advance to
- Press F3
- Observe that nothing happens
- Instead, go to Menu -> Edit -> Find Next
- Observe that this works correctly and advances to the next match
- Open the key bindings settings and search for F3
- Observe that F3 is bound to both "Find Next" and "Add Hardware Breakpoint"
Expected Behavior:
Pressing F3 should trigger Find Next, consistent with using Menu -> Edit -> Find Next. F3 should not be bound to two conflicting actions ("Find Next" and "Add Hardware Breakpoint") such that one silently fails to trigger.
- 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 ·
-
Arch: MSP430
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8516 · 1 assignee ·
-
Arch: MSP430
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Vector35/binaryninja-api#8503 · 1 assignee ·
-
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 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·