For the complete documentation index, see llms.txt. This page is also available as Markdown.

Jump Anywhere

Jump Anywhere is IDA's unified navigation dialog — a single entry point for jumping to any location in the IDB. It accepts a broader range of inputs: names, addresses, expressions, tokens, and identifiers from multiple namespaces.

Jump! dialog

Invocation

  • Press G to open Jump Anywhere from any view, or navigate to Jump → Jump anywhere....

  • Press G to jump back to the last address visited via Jump Anywhere.

  • If you prefer the legacy G shortcut behavior bound with Jump to address, you can enable it under Options → Feature Flags.

The dialog opens in history mode — your previous jumps, with their results, one keystroke away (entries from other databases collapse to grey query-only rows).

Jump anywhere - history mode
Jump anywhere - cross-binary history mode

What You Can Type

Numbers

Format
Example

Hex with 0x prefix

0x401000

Hex without prefix (default base)

401000

Decimal

4198400

Octal

0777

Binary

0b101010

Named Symbols

  • Regular names: main, printf, etc.

  • Dummy names: sub_401000, loc_4010A0, byte_402000, …

  • seg+offset

Current-IP Tokens

Token
Meaning

$

Current address

.

Current address (alias)

_

Current address (alias)

ash.a_curip

Processor-dependent current-IP token

Address Interpretation

When the input parses to a number, Jump Anywhere presents it as up to three candidates:

  • VA — virtual address

  • RVA — relative to image base

  • File offset

Segment-Relative Addresses

seg:off form — for example, fs:30 during debugging.

Arithmetic

You can combine any of the above with arithmetic:

Frame / Function-Local Identifiers

  • Stack-frame variables of the current function

  • Local labels of the current function

Type-System Identifiers

  • Enum symbolic constants

  • Local-type names — UDM members are resolvable when Jump Anywhere is invoked from a type listing

Expression-Language Identifiers

  • IDC / current extlang expressions: cpu.EIP, etc.

  • User-defined extlang globals — IDC extern variables, Python globals, etc. Usable inside arithmetic: main + kq where kq is a user-defined symbol

Use the Evaluate expressions with dropdown in Jump Anywhere options to select the expression-evaluation language. Python globals are only visible when Python is selected.

Result List

  • Use / / PageUp / PageDown / Home / End to navigate the list.

History rows preview their recorded destination, in the view they were jumped to; entries from other databases show a blank pane.

Preview pane

Every navigable row previews live as you move through the list — Disassembly, Pseudocode (already-decompiled functions only), or Hex.

Preview pane - Pseudocode
Preview pane - Hex

The segmented buttons next to the input pick the view and remember your preference. Local-type results preview as a type listing; expression results preview their resolved target.

The preview pane can be disabled under Options → Feature Flags.

Options

Open the Jump Anywhere options dialog from within the Jump! dialog to configure its behavior. Click the options button in the top-right corner.

Jump! dialog - options
Jump anywhere options

When reopening:

Option
Effect

Show recent navigations

Opens the dialog in history mode (default).

Restore last query results

Reopens with the previous query and its results pre-loaded.

Evaluate expressions with:

Controls the expression-evaluation language used to resolve extlang expressions and globals. Set to None to disable extlang evaluation.

Configuration

Setting
File
Effect

JUMP_ANYWHERE_MAX_RESULTS

idagui.cfg

Maximum number of result rows shown

JUMP_ANYWHERE_MAX_HISTORY

idagui.cfg

Maximum number of past queries kept in history

ENABLE_INDEXER

ida.cfg

Enables the indexer subsystem that powers the search. Enabled by default.

Limitations

  • Search relies on the indexer. With ENABLE_INDEXER=NO, the dialog still parses literal inputs (addresses, names) but doesn't perform similarity search.

  • Names defined after the index was built may not appear in results until the index catches up. The indexer runs asynchronously after the database changes.

Last updated

Was this helpful?