About 736,000 results
Open links in new tab
  1. Memory (Debugging with GDB) - sourceware.org

    The addresses and contents printed by the x command are not saved in the value history because there is often too much of them and they would get in the way. Instead, GDB makes these …

  2. How to modify memory contents using GDB? - Stack Overflow

    Jul 22, 2010 · I know that we can use several commands to access and read memory: for example, print, p, x... But how can I change the contents of memory at any specific location …

  3. Examining Memory With a Debugger - Sonoma State University

    Fortunately, gdb provides another command for examining the contents of memory directly—that is, the actual bit patterns. In order to use this command, we need to determine the actual …

  4. Debugging with GDB - Examining Data

    GDB prints memory addresses showing the location of stack traces, structure values, pointer values, breakpoints, and so forth, even when it also displays the contents of those addresses. …

  5. Debugging with GDB - Memory - GNU

    The contents of that address, as examined, are available in the convenience variable $__. If the x command has a repeat count, the address and contents saved are from the last memory unit …

  6. Can GDB Change the Assembly Code of a Running Program? A ...

    Nov 25, 2025 · One question that often arises is: *Can `gdb` modify the assembly code of a running program in real-time?* The short answer is **yes**—but with caveats. `gdb` lets you …

  7. GDB Tutorial for Reverse Engineers: Breakpoints, Modifying ...

    Apr 8, 2021 · Modifying memory is similar to modifying registers in the sense that any memory location can be a variable in GDB. So in my example, I want to change the contents of the …

  8. Gdb/Memory - Get docs

    Within GDB and this document, the term addressable memory unit (or memory unit for short) is used when explicitly referring to a chunk of data of that size. The word byte is used to refer to …