Alternatives
Products that do what Debugly does
stack trace made easy
- 1DF
2019 · github.com
- 2DJ
2023 · github.com
- 3
- 4CA
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
- 5HA
Hi, I created httpdbg, a tool for Python developers to easily debug HTTP(S) client requests in Python programs. I developed it because I needed a tool that could help me trace the HTTP requests sent by my tests back to the corresponding methods in our API client. The goal of this tool is to simplify the debugging process, so I designed it to be as simple as possible. It requires no external dependencies, no setup, no superuser privileges, and no code modifications. I'm sharing it with you today because I use it regularly, and it seems like others have found it useful too—so it might be…
2024 · github.com
- 6TC
Hey HN Community, For years I’ve received bug reports with stack traces that were garbled and hard to read. It’s easy enough to use a regular expression to fix them, but I noticed that some folks on my team hadn’t thought to do that. So, I created TidyTrace.com to quickly and easily do it for my team members. For example, take this Java stack trace Exception in thread "main" java.util.InputMismatchException\n\tat java.base/java.util.Scanner.throwFor(Scanner.java:939)\n\tat java.base/java.util.Scanner.next(Scanner.java:1594)\n\tat…
2024 · tidytrace.com
- 7GA
2022 · github.com
- 8DS
2022 · github.com
- 9UC
2023 · github.com
- 10LD
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
- 11
- 12UR
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
- 13FA
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
- 14PI
Ladies and gentlemen of a Lisp persuasion, Clojurians and Clojuristas, followers of the paren and everyone else covetously eyeing the greener grass, I made an open-source thing that I would like to share with you. My elevator pitch is that it'll make you forget all about regular print debugging in 10 minutes straight. The slightly longer pitch is this: #>(tag'n'trace any Clojure(-Script) form to `tap>` and Portal with automatic last-input function replay on eval, instant re-render and hassle-free insertion of traced data into the REPL) And before I end up pasting half the README here in bits…
2023 · github.com
- 15WP
Hello, Are you curious to discover which snippets of your code were copied from Stackoverflow? Where else on the Internet are those icons that you copied a long time ago? Or simply to discover which licenses apply to the open source in your code? There's an app for that: http://triplecheck.net/quantum/ Development of this tooling took over two years, we archived over 630Tb of open source data around the web. Some sources of data have gone offline in the meanwhile but we kept a copy for posterity. Things to consider: - Stackoverflow snippet detection is limited to Java at…
2016
- 16PA
2015 · github.com
- 17
- 18IB
Hi HN, I built this because I got tired of the Claude Code CLI hiding details from me. Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts. I wanted a middle ground: *Full observability without the noise.* `claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time. *Unlike wrappers, it solves the visibility gap in your native…
Feb 2026 · github.com
- 19SF
2013 · stackifier.com
- 20IR
Sharing an internal tool that accelerated my development work 10-fold, especially with API debugging. Thought fellow developers here might find it useful. As a developer, I often have trouble reproducing errors at the client end. https://intercept.rest lets me debug and monitor API requests and responses. It is similar to the Network tab in Chrome Developer Tools but works for any API: mobile apps, webhooks, frontend etc. After I shared it with a close circle of friends, they found it incredibly useful and even found new use cases, I never imagined. Been a long time lurker here and…
2018
- 21TT
tracexec helps you to figure out what and how programs get executed when you execute a command. It's useful for debugging build systems, catching fd leaks, understanding what shell scripts actually do, figuring out what programs does a proprietary software run, etc.
2024 · github.com
- 22RA
Hi HN, I'm Damien, the solo founder of Recompyle. Self-funded. As a JavaScript developer, I have been annoyed by the console.log not being practical enough, and the debugger being 'too slow'. So I made Recompyle to fix that. It's kind of a mix of the console and the debugger. Plus, some file parsing to automatically log the start of the functions of the files you are working on.
2023 · recompyle.com
- 23IM
Mar 2026 · github.com
- 24TO
Hey Xinwei and Zecheng here, we are the authors of TraceRoot (https://github.com/traceroot-ai/traceroot). TraceRoot (https://traceroot.ai) is an open-source debugging platform that helps engineers fix production issues faster by combining structured traces, logs, source code contexts and discussions in Github PRs, issues and Slack channels, etc. with AI Agents. At the heart are our lightweight Python (https://github.com/traceroot-ai/traceroot-sdk) and TypeScript (https://github.com/traceroot-ai/traceroot-sdk-ts) SDKs -…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →