Work · alternatives · 2026
24 alternatives to Fatal Core Dump – A debugging murder mystery played with GDB
Debugging a crash can sometimes feel like a noir detective story: following faint clues, chasing red herrings, and eventually hitting the moment where the whole case finally makes sense. I leaned into that idea and built Fatal Core Dump, a small game where the investigation is real crash debugging. The game gives you a Linux binary, its core dump, a source file, and some logs. You solve the mystery by debugging it. The premise: an engineer dies when an airlock on an asteroid mining station opens unexpectedly. Your job is to determine whether it was a simple software bug or something more…
Fatal Core Dump is a debugging mystery game where players investigate a fatal airlock malfunction on an asteroid mining station. Using real Linux debugging tools like GDB, players analyze a provided binary, core dump… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1

The main homepage for ForensicDbg - your new modern crash debugger!
29d ago · forensicdbg.com · its alternatives →
- 2AW
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. https://jam.dev It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create). It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer…
2024 · its alternatives →
- 3

Hey! We are presenting CodeTracer - a user-friendly time-traveling debugger designed to support a wide range of programming languages: https://github.com/metacraft-labs/codetracer?tab=readme-ov-f... CodeTracer records the execution of a program into a sharable self-contained trace file. You can load the produced trace files in a GUI environment that allows you to move forward and backward through the execution and to examine the history of all memory locations. They say a picture is worth a thousand words — well, a video is even better! Watch the demo below to see…
2025 · github.com · its alternatives →
- 4

Helps analyze goroutines. Inspired by TDA for Java and goroutine-inspect for golang. - openziti/goroutine-analyzer
2022 · github.com · its alternatives →
- 5
Defrag the Game▲326Hi, A while ago, I came across this https://www.youtube.com/watch?v=KR3TbL3Tl6M on YouTube showing 8 hours of defragmenting a hard drive. For some reason, it inspired me to create this small game. Have fun :)
2024 · defrag-game.com · its alternatives →
- 6

Hey HN my name is Thassilo, I'm a student and passionate programmer from Germany. I want to showcase Spray, a small C debugger I've been working on for a few months now. Spray has a very simple and approachable interface. Its feature set is limited at this point, but it's already enough to tackle some basic problems. I stared to work on Spray because I was curious about how debuggers work. I am also trying to design Spray in such a way that it's easy to grasp and has a small mental overhead. I'd love to get your feedback on Spray. Email: d4kd (at) proton (dot) me PS: I'm generally interested…
2023 · github.com · its alternatives →
- 7

- 8

Hey HN, the is Chris, creator of FireDBG. We’ve been working on this debugger just about a year now. Time travel debugging isn’t a new concept, the new idea here is to use call tree visualisation to help us navigate the debug trace. It supports various Linux distros on x64 and macOS on x64 and M1. It’s only available for Rust right now, but we do want to bring this debugging experience to other programming languages. Please give it a try! Would love to know your thoughts. What’s your anecdote in debugging programs? My stupidity is usually in the form of: after a few hours of debugging, I…
2023 · firedbg.sea-ql.org · its alternatives →
- 9

Hi! I've been building a debugger on my nights and weekends because it's fun, and I personally need a better debugger for my work. GDB and LLDB pain me greatly; we can and will do better! As explained in the README, it's still very early-days and it's not ready for use yet, but check back often because it's improving all the time! Check out https://calabro.io/uscope for a more detailed explanation. Thanks for taking a look!
2025 · github.com · its alternatives →
- 10

Drop: a rootless Linux sandbox for developers. It isolates coding agents and third-party packages while preserving your work environment.
Sep 2026 · droprun.sh · its alternatives →
- 11CC
Chunk co-founder here. We spent the last 2 weeks building this to scratch our own itch: As developers, we often have problems that could be solved just by running a few lines of code. Sometimes, running this code on your local machine is fine. But other time, the code need to run automatically reacting to external events or to run continuously, which means, it needs to run on a server somewhere. So now, you have to find a cloud provider, to package or build the code and finally to deploy it. All of that for what could be literally be 4 lines of code. We couldn’t find an easier way to do…
2022 · chunk.run · its alternatives →
- 12AP
I built this because I wanted a fun way to practice incident debugging without the stress of an actual outage. You get a production incident scenario, read through logs and metrics, and figure out what went wrong. 9 scenarios so far across beginner to advanced. Built with Next.js. Free to play, no signup required to try it. Would love feedback on the scenarios - especially if you've dealt with real incidents that would make good puzzles.
Mar 2026 · youbrokeprod.com · its alternatives →
- 13

Hey HN, I tend to use printf-style debugging as my primary troubleshooting method and only resort to gdb as a last resort. While I like its ease of use printf debugging isn't without its annoyances, namely removing the print statements once you're done. I used to use trace-level logging from proper logging libraries but adding trace calls in every corner quickly gets out of control and results in an overwhelming amount of output. To scratch my own itch I created dlg - a minimal debugging library that disappears completely from production builds. Its API exposes just a single function, Printf…
2025 · github.com · its alternatives →
- 14

Tabs, splits, and tmux work fine until you have several projects open with logs, tests, and long-running shells. I kept rebuilding context instead of resuming work. Horizon puts shells on an infinite canvas. You can arrange them into workspaces and reopen later with layout, scrollback, and history intact. Built in 3 days with Claude/Codex, dogfooding the workflow as I went. Feedback and contributions welcome.
Mar 2026 · github.com · its alternatives →
- 15

How quickly can you debug an error in a distributed system?
2019 · lightstep.com · its alternatives →
- 16

A dbg(…) macro for C++. Contribute to sharkdp/dbg-macro development by creating an account on GitHub.
2019 · github.com · its alternatives →
- 17

From the creators of rebar3_format, here comes… rebar3_hank, a powerful but simple tool to detect dead code around your Erlang codebase (and kill it with fire!)
2021 · tech.nextroll.com · its alternatives →
- 18

Hey everyone! I’m excited to share a project I’ve been working on throughout my university studies. It’s called BiTE (https://github.com/WINSDK/bite) and it's a tool primarily focused on being an executable viewer with reverse engineering capabilities. BiTE supports Windows, MacOS, and Linux, along with their associated executable formats. It’s also capable of parsing and displaying debug information using DWARF/PDB formats, which I hope will be useful even for just comparing codegen. I’ve put a lot of effort into this and it's the first time I'm releasing something…
2024 · github.com · its alternatives →
- 19

ChunkHound’s goal is simple: local-first codebase intelligence that helps you pull deep, core-dev-level insights on demand, generate always-up-to-date docs, and scale from small repos to enterprise monorepos — while staying free + open source and provider-agnostic (VoyageAI / OpenAI / Qwen3, Anthropic / OpenAI / Gemini / Grok, and more). I’d love your feedback — and if you have, thank you for being part of the journey!
Jan 2026 · github.com · its alternatives →
- 20

An alternative to stack traces for your Go errors. Contribute to bracesdev/errtrace development by creating an account on GitHub.
2023 · github.com · its alternatives →
- 21

Debugging-friendly exceptions for Python. Contribute to cknd/stackprinter development by creating an account on GitHub.
2019 · github.com · its alternatives →
- 22

A simple way to output stack traces when a program crashes in C++, using the new C++23 <stacktrace> header - TylerGlaiel/Crashlogs
2023 · github.com · its alternatives →
- 23

This project is inspired by some of the asserts in Unreal engine. Due to reliance on core_intrinsics it is necessary to develop using nightly Rust, but there are stubs in place so a production build will not require nightly. I recently released version 0.2 which includes no_std support and adds optional log message arguments to the ensure macro.
2024 · github.com · its alternatives →
- 24

Rust debugger for Linux x86-64. Contribute to godzie44/BugStalker development by creating an account on GitHub.
2025 · github.com · its alternatives →
Also compare
- I built a post-mortem debugger for native Windows x64/x86 crashes alternatives
- A web debugger an ex-Cloudflare team has been working on for 4 years alternatives
- CodeTracer – A time-traveling debugger implemented in Nim and Rust alternatives
- Goroutine-analyzer: A visual goroutine stack dump debugging tool alternatives
- Defrag the Game alternatives
- I spent 6 months building a C debugger as a 17-year-old alternatives
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →