# GDB (GNU Debugger)

29 Hacker News commenters recommended GDB (GNU Debugger) and 16 criticized it, November 2025 to November 2026. It was recommended in 10 of 13 months.

**Verdict:** Free command-line debugger that people rely on for crash analysis, core dumps, and assembly work, often driven from a terminal or editor. Critics say it handles C++ types poorly and has weak tracing support.

## Why people recommend it

- Works from terminal and editors (5 comments): "gdb and others have perfectly fine text mode interfaces" ([source](https://news.ycombinator.com/item?id=47556701)) "I have inline debugging with gdb in neovim." ([source](https://news.ycombinator.com/item?id=46289947)) "I also love the simplicity of c vim and gdb" ([source](https://news.ycombinator.com/item?id=48475225))
- Good for assembly and low-level work (4 comments): "Gdb is an excellent debugger for assembly, even when the original code was written in C" ([source](https://news.ycombinator.com/item?id=50269554)) "Running gdb as subprocess, with breakpoints, step, run, continue, is the basic stuff." ([source](https://news.ycombinator.com/item?id=48189716)) "that's can be done via GDB as well - save RAM + registers and then load them back" ([source](https://news.ycombinator.com/item?id=47188278))
- Useful for debugging almost anything (4 comments): "GDB (or lldb, or valgrind, etc.) is useful for debugging just about anything." ([source](https://news.ycombinator.com/item?id=48135668)) "It helps to mess around a lot with smaller programs in gdb or lldb" ([source](https://news.ycombinator.com/item?id=48081165)) "debugging it is relatively sane with gdb" ([source](https://news.ycombinator.com/item?id=46947126))
- Essential for crash and core dump analysis (2 comments): "The great thing about such crashes is if you have coredumps enabled that you can just load the crashed binary into GDB and type 'where'" ([source](https://news.ycombinator.com/item?id=45845745)) "being able to just fire up gdb and get an immediate landscape of what the issues were in the program was just invaluable" ([source](https://news.ycombinator.com/item?id=47113743))

## What people warn about

- Slow or weak tracing support (3 comments): "gdb thread apply all bt is slow but does full call stack walking" ([source](https://news.ycombinator.com/item?id=46753899)) "the tracing support is so bad in gdb" ([source](https://news.ycombinator.com/item?id=46432141)) "GDB and perf are not even in the same league." ([source](https://news.ycombinator.com/item?id=46260214))
- Poor C++ type and data display (2 comments): "I'm unhappy with the tooling GDB/LLDB provide for displaying and debugging this information" ([source](https://news.ycombinator.com/item?id=46114498)) "handlig c++ types with gdb can be a nightmare" ([source](https://news.ycombinator.com/item?id=46045457))
- Fails on corrupted stacks or segmented memory (2 comments): "the cherry on top is that gdb just stops being useful since it doesn't know anything about segmented memory" ([source](https://news.ycombinator.com/item?id=47858531)) "I stopped using it once it would break when the stack became corrupted and haven't tried it since." ([source](https://news.ycombinator.com/item?id=47402537))

## Alternatives hackers recommend

- [WinDbg](https://hackerapproved.com/p/windbg.md): 14 recommend
- [HyperProbe](https://hackerapproved.com/p/hyperprobe.md): 12 recommend
- [RenderDoc](https://hackerapproved.com/p/renderdoc.md): 10 recommend
- [RAD Debugger](https://hackerapproved.com/p/rad-debugger.md): 7 recommend
- [rr by Mozilla](https://hackerapproved.com/p/rr.md): 7 recommend

## Cite as

Hacker Approved, "GDB (GNU Debugger)", https://hackerapproved.com/p/gdb/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).