edb-debugger
1.5.0 open-sourceThe section your link pointed to isn't on edb-debugger's page any more, so we've brought you to the top.
edb-debugger is a cross platform AArch32/x86/x86-64 debugger for Linux, with ports underway for FreeBSD, OpenBSD, OSX, and Windows.
./edb --symbols <filename>
./edb --run /bin/ls /etc /bin
edb --args "my app" "file with space.txt"
Debugger::log("User %s connected from %s", username, ip_addr)
Summary
edb-debugger is an open-source debugger for reverse engineering x86, x86-64, and AArch32 binaries, distributed under GPL 2, so it costs nothing to use. It runs as a desktop application with a Qt-based GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands., and while ports for other Unix-like systems and Windows are in progress, Linux is the only officially supported platform. It's aimed at reverse engineers and binary analysts who need to step through and inspect native code rather than manage source. Its README describes it as inspired by OllyDbg, positioning it as a Linux-native counterpart to that Windows tool. The project traces back to 2011 and has drawn 45 contributors, with commits in the past year, though its last formal release was well over two years ago.
edb-debugger is a cross platform AArch32/x86/x86-64 debugger for Linux, with ports underway for FreeBSD, OpenBSD, OSX, and Windows.
How edb-debugger helps
What is this native binary actually doing when it hits this crash?
steps through the disassembly instruction by instruction, showing register and stack state at the point of failure so you can see the exact code path that led there
Where in the code does this program branch based on a value I control?
sets breakpoints on execution and lets you inspect registers and memory live, so you can trace which comparisons and jumps depend on your input
What is stored at this address right before the program misbehaves?
shows a live memory view keyed to the current instruction pointer, so you can watch values change as execution proceeds toward the fault
Which instruction is responsible for corrupting this register or pointer?
lets you set breakpoints and single-step through the surrounding code, comparing register contents before and after each instruction to isolate the culprit
Can I change a value mid-execution to see how the program reacts?
lets you edit registers and memory directly while the process is paused, then resume execution to observe the effect
Languages
Command line
No command matches.
| 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.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for edb-debugger, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail edb-debugger 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
55 entries
No entries match these filters.
- March 20241
- April 20201
- October 20102
- July 20101
- March 20101
- February 20101
- October 20091
- July 20092
- June 20091
- February 20091
- January 20091
- December 20083
- August 20081
- July 20084
- June 20081
- May 20081
- April 20081
- February 20081
- January 20081
- December 20071
- November 20073
- October 20072
- September 20072
- August 20074
- July 20075
- May 20071
- April 20074
- March 20071
- December 20061
- November 20065
Project health
Issue, contributor and maintainer activity in eteran/edb-debugger, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 4 +4 vs prior 12 months
- Maintainers 1 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 4.1 years first maintainer reply 3.1 days
- Open backlog 66 of 564 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 66
- Contributors / month 1
- Commits / month 3
- Stars 2,961
- other 100%
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
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.