Alternatives
Products that do what I spent 6 months building a C debugger as a 17-year-old does
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…
- 1AW
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
- 2LD
Hi HN! We’re Adrien and Kanav. We met at our previous job, where we spent about a third of our lives combating a constant firehose of bugs. In the hope of reducing this pain for others in the future, we’re working on automating debugging. We’re currently working on a platform that ingests logs and then automatically reproduces, root causes and ultimately fixes production bugs as they happen. You can see some of our work on this here - https://news.ycombinator.com/item?id=39528087 As we were building the root-cause phase of our automated debugger, we realized that we developed…
2024 · github.com
- 3
- 4UA
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
- 5
- 6
- 7
- 8BC
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
- 9BA
Hey HN, we're developing Burr (github.com/dagworks-inc/burr), an open-source python framework that makes it easier to build and debug GenAI applications. Burr is a lightweight library that can integrate with your favorite tools and comes with a debugging UI. If you prefer a video introduction, you can watch me build a chatbot here: https://www.youtube.com/watch?v=rEZ4oDN0GdU. Common friction points we’ve seen with GenAI applications include logically modeling application flow, debugging and recreating error cases, and curating data for testing/evaluation (see…
2024 · github.com
- 10
- 11HA
While helping one of my students create and iterate on a game in C using raylib, I realized there was quite a lot of time spent on experimenting with level design and colors, how the player moves, gravity, etc. and a lot of time was wasted making a change, exiting the game, recompiling, running the game, deciding his change wasn't right, and going through the whole cycle over and over. I could tell it was demotivating, and this process was creating a barrier that prevented him from experimenting to his heart's content. I started this project to solve this problem by giving a simple gui to a…
2024 · github.com
- 12WM
2025 · npmjs.com
- 13LL
Hey HN, I just built an experimental VSCode extension called LLM Debugger. It’s a proof-of-concept that lets a large language model take charge of debugging. Instead of only looking at the static code, the LLM also gets to see the live runtime state—actual variable values, function calls, branch decisions, and more. The idea is to give it enough context to help diagnose issues faster and even generate synthetic data from running programs. Here’s what it does: * Active Debugging: It integrates with Node.js debug sessions to gather runtime info (like variable states and stack traces). *…
2025 · github.com
- 14FA
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
- 15
- 16
- 17SL
Sidekick is a live application debugger that lets you troubleshoot your applications while they keep on running. It allows you to add dynamic logs and put non-breaking breakpoints in your running application without the need of stopping & redeploying. Currently supporting Java, Python & Node.js runtimes. Sidekick Open Source is here to allow self-hosting and make live debugging more accessible. Built for everyone who needs extra information from their running applications.
2022 · github.com
- 18MS
Hello HN community ! Finally I have a "Show HN" post. I'm bootstrapping my first Mac app, it's a standalone Xdebug PHP debugger. It aims to help any PHP developers out there who don't want to use IDE to debug code. My app it's slimmer, faster to load and easy to work and setup :) Hope you guys like it Site: http://codebugapp.com/
2012
- 19DB
My partner reviews a lot of P&IDs (piping and instrumentation diagrams) and the adjacent files involved (excel, docx, pdfs, acd/l5x, etc). In his company, these are usually done in Bluebeam. It's really hard to see the diff + keep track of all the revisions resulted by these iterations. They end up storing files like "rev3_final_redlined.pdf". We've been looking for something close to Github to do these reviews, but haven't found one easy enough for folks with no CLI experience to understand and use (happy to check out more tools if you know any). So I built withkord.com to help with…
Aug 2026 · withkord.com
- 20FC
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…
Mar 2026 · robopenguins.com
- 21DZ
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
- 22BD
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. It’s called Jam (jam.dev) and it prevents product managers (like I used to be) from being able to create completely 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. I used to write in the ticket that something didn’t work— only to lead to a ton of confusion by the engineer what I meant by “didn’t work”. Was the button unresponsive? Did the page crash? Did it return an error? Or like sometimes I thought…
2024
- 23EC
I participated in the Nvidia + Vercel 2 hour hackathon in SF tonight, and built something I've wanted, but hadn't tried building. I implemented an MCP Server and VS Code extension to allow Claude Desktop to place breakpoints, step through code, and execute expressions (assuming language support). So you can ask it a question that requires actually stepping through the code and now it can actually do that - check values for you, etc. It's _definitely_ not perfect. Have improvements? Please make a PR!
2025 · github.com
- 24LO
Show HN: Leaping - Open-source debugging with LLMs Hi HN! We’re Adrien and Kanav. We met at our previous job, where we spent about a third of our life combating a constant firehose of bugs. In the hope of reducing this pain for others in the future, we’re working on automating debugging. We started by capturing information from running applications to then ‘replay’ relevant sessions later. Our approach for Python involved extensive monkey patching: we’d use OpenTelemetry-style instrumentation to hook into the request/response lifecycle, and capture anything non-deterministic (random,…
2024
Ranked by how close each launch is in meaning, then by votes. Refine with a description →