valgrind

Diagnose memory errors and profile Linux applications with Valgrind and Callgrind.

Updated Aug 27, 2026

Search Tags:#debugging #memory #profiling #linux #valgrind #callgrind

Ready to run

npx skills add https://github.com/fasterthanlime/_claude --skill valgrind

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: valgrind
Source: https://github.com/fasterthanlime/_claude/tree/main/skills/valgrind
Command: npx skills add https://github.com/fasterthanlime/_claude --skill valgrind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug crashes, memory corruption, leaks, and performance hotspots using Valgrind and Callgrind on Linux, with guidance for interpreting outputs and GUI tools.

Core Features & Use Cases

Memory Debugging: Detect leaks, invalid reads/writes, and uninitialized memory.
Track Origins: Identify where an uninitialized value originates.
Profiling: Use Callgrind to analyze function-level performance and compare before/after runs.
GUI Analysis: Visualize results with kcachegrind/qcachegrind for easier insight.

Quick Start

Run a Linux binary under Valgrind, e.g., valgrind --leak-check=full --error-exitcode=1 ./target/debug/mybin, then inspect the output for leaks and traces.

Frequently Asked Questions about valgrind

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect memory leaks in my Linux application?▼

Memory leaks are detected by running your binary under Valgrind with the --leak-check flag, which scans for unreleased heap memory. Run valgrind --leak-check=full ./your_binary to identify leak sources and stack traces showing where memory was allocated but never freed.

What's the best way to find where an uninitialized value originates?▼

Use Valgrind's --track-origins flag to trace uninitialized memory back to its source. This reveals the exact allocation point where a value was never initialized, helping you fix the root cause rather than just the symptom.

Can I profile function-level performance and identify bottlenecks on Linux?▼

Yes, Callgrind profiles your application to collect function call counts and cycle costs. Analyze the output with GUI viewers like kcachegrind or qcachegrind to visualize call graphs, compare before/after runs, and pinpoint performance hotspots.

How do I integrate memory and performance debugging into my development workflow?▼

Run Valgrind and Callgrind as part of your testing pipeline, using flags like --error-exitcode to fail builds on memory errors. Output formats support scripting and test integration, enabling automated detection of crashes, corruption, and leaks.

Does Valgrind work on macOS or only Linux?▼

Valgrind is primarily designed for Linux. macOS support is limited and experimental, making Linux the recommended platform for reliable memory debugging and profiling workflows.