gdb-peda
open-sourceThe section your link pointed to isn't on gdb-peda's page any more, so we've brought you to the top.
GDB plugin that enhances exploit development with colorized disassembly, ROP gadget search, pattern generation, and shellcode utilities.
Summary
gdb-peda is an open-source GDB plugin, free to use, that adds colorized register, memory, and disassembly displays along with commands for exploit development, and you run it by sourcing peda.py from your .gdbinit so it loads inside your normal gdb session on the command line. It suits exploit developers and reverse engineers who work directly in gdb, giving them commands like checksec, ropgadget, pattern, and dumpargs without leaving the debugger. It sits in the same space as gdb enhancement plugins such as GEF or pwndbg, though the README does not name them directly. Development looks inactive: the project dates back to 2012, has drawn 29 contributors, but has seen no commits in the past year and only a single release in the window tracked, so it is worth checking whether it still handles current binaries and gdb versions before relying on it.
GDB plugin that enhances exploit development with colorized disassembly, ROP gadget search, pattern generation, and shellcode utilities.
How gdb-peda helps
Does a binary in front of me have stack protections or other exploit mitigations enabled?
inspects the loaded ELF and reports the security options built into it, such as canaries and other protections, in one command
What are the usable ROP gadgets in this binary or its loaded libraries?
scans the specified memory range or module and lists the gadgets it finds, without needing a separate gadget-search tool
Where does a crashing input land, and how far into it is the overwrite?
generates a cyclic pattern, writes it to memory, and once the process stops, searches registers or memory for that pattern to report the exact offset
Which memory regions belong to which loaded sections of the running process?
reports the virtual mapping ranges of the debugged process broken down by section
Is there a plaintext key or known byte pattern hiding somewhere in this process's memory?
runs a search across memory for a literal or regular-expression pattern and reports the matching addresses
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Release-note detail over time
See how much detail gdb-peda puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in longld/peda, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 46 of 101 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 46
- Contributors / month 0
- Commits / month 0
- Stars 6,150
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →