address-sanitizer

Detect memory errors in C/C++ fuzzing with AddressSanitizer.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/erenisiklar/Pusula --skill address-sanitizer-erenisiklar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address-sanitizer
Source: https://github.com/erenisiklar/Pusula/tree/main/.claude/skills/address-sanitizer
Command: npx skills add https://github.com/erenisiklar/Pusula --skill address-sanitizer-erenisiklar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AddressSanitizer detects memory errors during fuzzing, helping teams identify memory corruption, buffer overflows, and use-after-free bugs early in development.

Core Features & Use Cases

  • Instrument code at compile time to detect invalid memory operations.
  • Shadow memory tracking provides precise detection of memory safety violations with minimal performance impact.
  • Generates detailed crash reports with stack traces, allocation traces, and reports to help triage fuzzing failures.
  • Use Case: When fuzzing C/C++ code, enable ASan to reveal memory bugs that might crash or corrupt data in production environments.

Quick Start

Compile your targets with -fsanitize=address and run your fuzz harness to observe memory-error reports.

Frequently Asked Questions about address-sanitizer

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

FAQPage Schema
How do I detect buffer overflows and use-after-free bugs when fuzzing C/C++ code?▼

To detect buffer overflows and use-after-free bugs during fuzzing, compile your C/C++ targets with the -fsanitize=address flag and run your fuzz harness to generate detailed memory error reports.

What is AddressSanitizer and how does it find memory corruption during fuzzing?▼

AddressSanitizer is a compile-time instrumentation tool that uses shadow memory tracking to precisely detect memory safety violations, catching invalid memory operations with minimal performance impact during fuzzing.

How do I get detailed stack traces and allocation traces for fuzzing crashes?▼

You can get detailed stack traces and allocation traces for fuzzing crashes by compiling with -fsanitize=address and configuring runtime options to produce comprehensive reports for triaging memory failures.

Can I use AddressSanitizer in development and test pipelines for C/C++ memory safety?▼

Yes, you can use AddressSanitizer across development and test pipelines to instrument C/C++ code, revealing memory bugs like double-free issues that might crash or corrupt data in production environments.

What types of memory safety violations does AddressSanitizer catch during fuzzing?▼

AddressSanitizer catches memory safety violations including buffer overflows, use-after-free bugs, double-free issues, and other memory corruption by tracking invalid memory operations at compile time.

Does AddressSanitizer have a high performance impact when checking for memory errors?▼

AddressSanitizer has minimal performance impact during fuzzing, using shadow memory tracking to provide precise detection of memory safety violations without significantly slowing down test pipelines.