debugging

Guide C++ bug reproduction, isolation, and correction with GDB, LLDB, and sanitizers.

6|1|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-cpp --skill debugging-pluginagentmarketplace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/pluginagentmarketplace/custom-plugin-cpp/tree/main/skills/debugging
Command: npx skills add https://github.com/pluginagentmarketplace/custom-plugin-cpp --skill debugging-pluginagentmarketplace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

C++ debugging can be time-consuming and error-prone; this skill provides a production-grade, guided approach to reproduce, isolate, instrument, and resolve issues efficiently.

Core Features & Use Cases

  • GDB/LLDB mastery for runtime analysis and crash investigation
  • Sanitizers, memory debugging, and crash analysis for robust bug detection
  • Systematic bug investigation techniques with step-by-step workflows

Quick Start

Identify a failing scenario and ask me to guide you through reproducing, isolating, instrumenting, and resolving the bug.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I debug a C++ crash using GDB and LLDB?

To debug a C++ crash, this skill guides you through GDB and LLDB commands for runtime analysis, helping you reproduce the issue, isolate the fault, and investigate the crash systematically.

What is the best way to find memory leaks in C++ with sanitizers?

The best way to find memory leaks is using sanitizers and memory debugging techniques, which this skill covers to detect bugs robustly and guide you through safe instrumentation and correction steps.

Can I use this to isolate bugs in production-like C++ environments?

Yes, it supports systematic bug investigation across development, test, and production-like scenarios, providing structured debugging workflows and configurable tool usage tailored to your specific environment.

How do I set up a systematic C++ debugging workflow from scratch?

You start by identifying a failing scenario, then this skill walks you step-by-step through reproducing, isolating, instrumenting, and resolving the bug with structured workflows and error handling.

Do I need pyyaml installed to use the C++ debugging workflows?

Yes, pyyaml is a required dependency, likely used for configuring debugging workflows and tool usage parameters before you begin instrumenting and resolving your C++ memory or crash issues.

Why should I use a systematic approach instead of manual C++ debugging?

A systematic approach prevents time-consuming and error-prone guesses by enforcing reproducibility and isolation steps, ensuring you safely instrument code and resolve issues efficiently using GDB, LLDB, and sanitizers.