sharkdp/dbg-macro

A dbg(…) macro for C++

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 40 minutes ago
Type:Library / SDKCategory(s):Debugging & ProfilingDeveloper Tools
Added to GitGenius on September 21st, 2026
Created on June 19th, 2019
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 273
Total Stargazers: 3,234 (+0)
Total Subscribers: 46 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.7 hours
Mean response time: 24.9 days
90th percentile: 107.1 days
Tracked items: 6

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,276 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • good first issue (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

dbg-macro is a debugging macro for C++ that provides convenient print-based debugging output.

The macro solves the problem of verbose, repetitive debugging output by offering a compact syntax for inspecting variable values during development. Rather than writing manual print statements with format specifiers, developers call dbg(variable) and the macro automatically prints the variable name, its value, and source location information. This approach reduces boilerplate while making debug output more readable and consistent across a codebase.

The tool suits developers who prefer print-based debugging over interactive debuggers, particularly in rapid prototyping or when working in environments where debuggers are inconvenient. It works well in small to medium projects where quick iteration matters more than sophisticated debugging infrastructure. The macro integrates into existing C++ codebases with minimal setup since it requires only header inclusion.

Development on the project is sparse and infrequent, with long gaps between updates. The maintainer responds to issues and pull requests when they arrive but does not actively drive the project forward with new features or regular maintenance cycles.