# x86-64 Executables

[x86-64 Documentation](https://asm-editor.specy.app/documentation/x86.md)

Web page: https://asm-editor.specy.app/documentation/x86/executables

Import and debug an x86-64 Linux executable, read and edit its bytes, inspect its Listing, patch instructions during a paused run, and open the program a Build links.

31 entries, each with its own page of markdown:

- [Running an Executable](https://asm-editor.specy.app/documentation/x86/executables/overview.md): An Executable is a compiled x86-64 Linux ELF binary.
- [What runs](https://asm-editor.specy.app/documentation/x86/executables/what-runs.md): The emulator runs 64-bit x86 Linux ELF executables: Statically linked: all library code is included inside the executable.
- [Shared libraries](https://asm-editor.specy.app/documentation/x86/executables/libraries.md): Dynamically linked executables can use five bundled system libraries (from Ubuntu 26.04), downloaded automatically on first use: Library Version Purpose…
- [The Hex editor](https://asm-editor.specy.app/documentation/x86/executables/hex-editor.md): Switch to Hex in the dock to inspect the file's raw bytes.
- [Editing bytes](https://asm-editor.specy.app/documentation/x86/executables/byte-edits.md): Click any byte in the Hex editor to place the caret: Type hexadecimal digits in the hex column or printable ASCII characters in the text column to overwrite…
- [Parts of the ELF file](https://asm-editor.specy.app/documentation/x86/executables/elf-parts.md): When viewing an Executable, the Hex editor color-codes the structure of the ELF file: Code sections (such as .text) Data sections (such as .rodata and .data)…
- [Finding bytes](https://asm-editor.specy.app/documentation/x86/executables/finding.md): Use the toolbar above the Hex editor to search and navigate: Find (Ctrl+F): Search for Hex bytes or case-sensitive Text.
- [The data inspector](https://asm-editor.specy.app/documentation/x86/executables/data-inspector.md): Click Inspector above the Hex editor to decode the bytes starting at the caret as signed and unsigned integers (int8 through uint64) and floating-point numbers…
- [The Listing](https://asm-editor.specy.app/documentation/x86/executables/listing.md): Disassemble opens the Executable's Listing: a read-only view of its machine code in NASM syntax followed by its data sections (db, dq, resb).
- [Names in the Listing](https://asm-editor.specy.app/documentation/x86/executables/names.md): When an Executable retains its symbol tables, the Listing uses those names; when symbols have been stripped, it generates deterministic names from file offsets…
- [C++ names](https://asm-editor.specy.app/documentation/x86/executables/cpp-names.md): C++ compilers mangle namespaces, classes, and parameter types into symbol names such as _ZNSolsEi.
- [The Symbols panel](https://asm-editor.specy.app/documentation/x86/executables/symbols.md): Open the Symbols panel (the tags icon in the left rail) to browse all Functions and Strings in the current Executable: Filter: Type in the filter box to match…
- [Decompile](https://asm-editor.specy.app/documentation/x86/executables/decompile.md): Decompile opens a Pseudocode pane beside the Listing, using Ghidra's decompiler to translate the current function's machine code into C-like code.
- [Reading the Pseudocode](https://asm-editor.specy.app/documentation/x86/executables/pseudocode.md): The Pseudocode header comment shows the function's name and address range (// main, 0x5555555551e9 to 0x5555555552ba), followed by your function comment if any.
- [When decompiling takes long](https://asm-editor.specy.app/documentation/x86/executables/decompile-time.md): Most functions decompile in a fraction of a second.
- [Renames](https://asm-editor.specy.app/documentation/x86/executables/renaming.md): You can rename any function, global data label, string label, local jump target (.LAB_1), or Pseudocode variable/parameter to make the code easier to follow.
- [Comments](https://asm-editor.specy.app/documentation/x86/executables/comments.md): You can attach notes to individual instructions/statements or to an entire function.
- [Keeping renames and comments](https://asm-editor.specy.app/documentation/x86/executables/annotations.md): Renames and comments have their own undo history across the Listing, Pseudocode, and Symbols panel: Press Ctrl+Z (⌘Z on Mac) or choose Undo rename or comment…
- [Searching the Project](https://asm-editor.specy.app/documentation/x86/executables/search.md): Press Ctrl+Shift+F (⌘⇧F on Mac) or click the magnifying glass in the left rail to open the Search panel.
- [Searching the Pseudocode](https://asm-editor.specy.app/documentation/x86/executables/search-pseudocode.md): When Pseudocode is enabled under Look in, the Search panel decompiles the Executable's functions in the background—starting with main (or the entry point),…
- [Back and forward](https://asm-editor.specy.app/documentation/x86/executables/navigation.md): Every time you jump to a new location—via Go to Definition, Go to Symbol, Show in Listing, the Symbols panel, or Search results—the editor records your…
- [Building and stepping](https://asm-editor.specy.app/documentation/x86/executables/stepping.md): For an Executable, the Build button is labeled Debug.
- [Breakpoints](https://asm-editor.specy.app/documentation/x86/executables/breakpoints.md): Click in the gutter beside any instruction in the Listing—or press F9 / choose Toggle Breakpoint in the context menu—to set or remove a Breakpoint.
- [Debugging in the Pseudocode](https://asm-editor.specy.app/documentation/x86/executables/pseudocode-debugging.md): While debugging, the Pseudocode pane tracks the active function and highlights the statement corresponding to the current instruction.
- [Addresses in registers and memory](https://asm-editor.specy.app/documentation/x86/executables/memory.md): During a Debug session, the Memory view's address box accepts symbol names as well as hexadecimal addresses: Type any Listing label (main, FUN_brave_otter,…
- [The Command line and Arguments](https://asm-editor.specy.app/documentation/x86/executables/arguments.md): Enter command-line Arguments in the Command line bar at the top of the Terminal (or in Settings) before starting Debug or Build.
- [Testcases](https://asm-editor.specy.app/documentation/x86/executables/testcases.md): In the Testcases panel, each Testcase can supply standard input, command-line Arguments, initial register/memory values, and expected output or register/memory…
- [Patching an instruction](https://asm-editor.specy.app/documentation/x86/executables/patching.md): While a Debug session is paused, you can replace an instruction in memory to test how the program behaves (for example, flipping jne to je or replacing a check…
- [The Build output](https://asm-editor.specy.app/documentation/x86/executables/build-output.md): When you Build an x86 assembly or C/C++ program in the editor, the linked ELF executable is saved in the Explorer as the Build output (named after the Entry…
- [Log notes](https://asm-editor.specy.app/documentation/x86/executables/log-notes.md): The Log panel reports environment or instruction issues encountered during a run: Unimplemented syscalls: The call returns -ENOSYS to the program and logs the…
- [Safety](https://asm-editor.specy.app/documentation/x86/executables/safety.md): Executables run entirely inside your browser's WebAssembly sandbox, and both the Listing and Ghidra Pseudocode are generated locally on your device—binaries…
