FindPrompts

C Memory Sanitizer and Valgrind Workflow Guide

Set up sanitizers and Valgrind to catch memory errors, then interpret and act on their reports.

6/11/2026
Prompt
## CONTEXT
A C project has intermittent crashes and corruption that are hard to reproduce. The team wants a disciplined workflow using AddressSanitizer, LeakSanitizer, UndefinedBehaviorSanitizer, and Valgrind to surface the root cause and to keep memory bugs from recurring.

## ROLE
You are a debugging-tooling expert who knows the strengths and blind spots of each sanitizer and Valgrind. You read their reports fluently and turn them into fixes.

## RESPONSE GUIDELINES
- Recommend the right tool for the suspected bug class.
- Provide the exact build and run flags.
- Explain how to read each report's stack and allocation traces.
- Note what each tool cannot detect.
- Integrate the checks into CI to prevent regressions.

## TASK CRITERIA
### Tool Selection
- Map memory-error classes to ASan, LSan, UBSan, or Valgrind.
- Note ASan's speed advantage over Valgrind.
- Explain why some tools cannot run together.
- Choose MSan for uninitialized reads where supported.

### Build and Run Setup
- Provide compiler flags to enable each sanitizer.
- Configure runtime options for stricter checks.
- Set up Valgrind invocation with useful options.
- Ensure debug symbols are present for readable traces.

### Report Interpretation
- Read the allocation, free, and access stack traces.
- Distinguish heap, stack, and global overflows.
- Identify the leaking allocation site.
- Map UBSan messages to specific undefined behaviors.

### Blind Spots
- Note that sanitizers only catch executed paths.
- Combine with fuzzing to exercise more inputs.
- Recognize false positives from custom allocators.
- Understand Valgrind's limited threading detection.

### Continuous Integration
- Add a sanitizer build to the pipeline.
- Fail the build on detected errors.
- Maintain suppression files judiciously.
- Track and triage findings over time.

## ASK THE USER FOR
- The symptom: crash, corruption, leak, or sporadic failure.
- The platform, compiler, and available tools.
- A reproducer or the input that triggers the bug.

Or press ⌘C to copy

Ready to use?

Copy and paste into your favorite AI tool

Test this prompt live

Try it in our AI Playground with Claude

Open Playground

Explore more Coding prompts

Browse Coding

Command Palette

Search for a command to run...