You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the best things in a debugger is Run To Here debug command. That makes debugging faster.
But on Binary Ninja we don't have a key binding of it. Generally F4 is used for that:
App Name
Operation Name
Key Binding
IDA Pro
Run to cursor
F4
x64dbg
Run Until Selection
F4
Binary Ninja
Run To Here
not set
Quick and personal workaround: Ctrl + P (Command Palette) > Key Bindings and then set F4 for key binding.
My wish is; can you consider making F4 keybinding default for Run To Here debug command?
Thank you.
The text was updated successfully, but these errors were encountered:
Hello folks;
One of the best things in a debugger is
Run To Here
debug command. That makes debugging faster.But on Binary Ninja we don't have a key binding of it. Generally
F4
is used for that:Run to cursor
F4
Run Until Selection
F4
Run To Here
Quick and personal workaround:
Ctrl + P (Command Palette) > Key Bindings
and then setF4
for key binding.My wish is; can you consider making
F4
keybinding default forRun To Here
debug command?Thank you.
The text was updated successfully, but these errors were encountered: