Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Deadlog

almost drop-in mutex for debugging Go deadlocks

Details

External ID
46963736
Source
HN
Company
—
Product
Deadlog
Website domain
github.com
Launched
Feb. 10, 2026
Cohort
—
Upvotes
30
Upvotes percentile
0.7425876010781671
Tags
—
Fetched at
Sept. 7, 2026, 9:25 p.m.
Updated at
Sept. 7, 2026, 9:25 p.m.

Description

I've done this same println debugging thing so many times, along with some sed/awk stuff to figure out which call was causing the issue. Now it's a small Go package.With some `runtime.Callers` I can usually find the spot by just swapping the existing Mutex or RWMutex for this one.Sometimes I switch the mu.Lock() defer mu.Unlock() with the LockFunc/RLockFunc to get more detail defer mu.LockFunc()() I almost always initialize it with `deadlog.New(deadlog.WithTrace(1))` and that's plenty.Not the most polished library, but it's not supposed to land in any commit, just a temporary debugging aid. I find it useful.

Enrichment

Theme
Codex monitoring and optimization tools
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
debugging tool for go deadlocks
Manually corrected
False

Could you build this?

Yes It is a small Go debugging package that wraps sync.Mutex and sync.RWMutex with runtime stack trace captures to identify deadlocks.

Discussion

1 comment analyzed.

Competitors mentioned: synctest

Competitors

Other products that read as similar to this one — 51 launches clear the similarity bar, closest 8 shown.

Attention rank: #17 of 52 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 91 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.