F3 (Find Next) shortcut does not work, possibly due to conflict with Add Hardware Breakpoint key binding

[Weitao-Sun]

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:

1. Open a binary in Binary Ninja
2. Perform a search (e.g. via Find) so that Find Next has a target to advance to
3. Press F3
4. Observe that nothing happens
5. Instead, go to Menu -> Edit -> Find Next
6. Observe that this works correctly and advances to the next match
7. Open the key bindings settings and search for F3
8. 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.

[psifertex]

Probably a linux/windows only bug. On macos it's bound to CMD-G (likely why we've missed it).

Yeah: https://doc.qt.io/qt-6/qkeysequence.html?#:~:text=FindNext,Ctrl%2BG%2C%20F3

[xusheng6]

lol I had no idea that F3 is taken. What do you is a good way to fix it? Maybe just assign a different key to hardware breakpoint, e.g., F4?. The current one, iirc, is mirroring what x64dbg uses

[psifertex]

I think x64dbg is just mirroring windbg iirc too. I don't know the right answer. We could just move "find again" to CTRL-G on all platforms.