Stevenctl has released Deadlog, a Go package designed to simplify debugging mutex deadlocks. The tool offers a drop-in replacement for `sync.Mutex` and `sync.RWMutex`, making it easy to integrate into existing projects. Deadlog uses `runtime.Callers` to trace lock acquisitions, helping developers pinpoint the source of issues. This approach aims to streamline the often tedious process of identifying concurrency problems in Go code.

Deadlog provides a way to track unreleased locks, using `LockFunc()` and `RLockFunc()` to correlate RELEASED events. This allows the analyzer to detect locks that were acquired but never released. Users can also leverage named callsites using `WithLockName()` for more detailed logging, especially when dealing with multiple lock operations on the same mutex. The library then analyzes these logs.

By default, Deadlog writes events as JSON to standard output, but custom loggers and writers are supported. The package includes a CLI tool for analyzing log files, as well as a library for programmatic analysis. The analyzer identifies "Stuck" locks (START without ACQUIRED) and "Held" locks (ACQUIRED without RELEASED), offering a clear report. The project is available on GitHub.

This tool is especially useful for developers dealing with complex concurrent systems. The ability to quickly identify and diagnose deadlock issues can save considerable debugging time. Deadlog's ease of integration and detailed logging features create a practical solution for Go developers. The project has already gained 5 stars on GitHub, indicating early adoption and interest within the Go community.