[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F05BB8KF93EYK9FCKHB3CJ":3,"skill-same:01M7F05BB8KF93EYK9FCKHB3CJ":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7F05BB8KF93EYK9FCKHB3CJ","gdb-cli",null,"GDB debugging assistant for AI agents - analyze core dumps, debug live processes, investigate crashes and deadlocks with source code correlation","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgdb-cli\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: gdb-cli\ndescription: \"GDB debugging assistant for AI agents - analyze core dumps, debug live processes, investigate crashes and deadlocks with source code correlation\"\ncategory: development\nrisk: critical\nsource: community\ndate_added: \"2026-03-22\"\nauthor: Cerdore\ntags:\n- debugging\n- gdb\n- core-dump\n- crash-analysis\n- c++\n- c\ntools:\n- claude-code\n- cursor\n- gemini-cli\n- codex-cli\n- antigravity\n---\n\n# GDB Debugging Assistant\n\n## Overview\n\nA GDB debugging skill designed for AI agents. Combines **source code analysis** with **runtime state inspection** using gdb-cli to provide intelligent debugging assistance for C\u002FC++ programs.\n\n## When to Use This Skill\n\n- Analyze core dumps or crash dumps\n- Debug running processes with GDB attach\n- Investigate crashes, deadlocks, or memory issues\n- Get intelligent debugging assistance with source code context\n- Debug multi-threaded applications\n\n## Do Not Use This Skill When\n\n- The task is unrelated to C\u002FC++ debugging\n- The user needs general-purpose assistance without debugging\n- No GDB is available (GDB 9.0+ with Python support required)\n\n## Prerequisites\n\n```bash\n# Install gdb-cli\npip install gdb-cli\n\n# Or from GitHub\npip install git+https:\u002F\u002Fgithub.com\u002FCerdore\u002Fgdb-cli.git\n\n# Verify GDB has Python support\ngdb -nx -q -batch -ex \"python print('OK')\"\n```\n\n**Requirements:**\n- Python 3.6.8+\n- GDB 9.0+ with Python support enabled\n- Linux OS\n\n## How It Works\n\n### Step 1: Initialize Debug Session\n\n**For core dump analysis:**\n```bash\ngdb-cli load --binary \u003Cbinary_path> --core \u003Ccore_path> [--gdb-path \u003Cgdb_path>]\n```\n\n**For live process debugging:**\n```bash\ngdb-cli attach --pid \u003Cpid> [--binary \u003Cbinary_path>]\n```\n\n**Output:** A session_id like `\"session_id\": \"a1b2c3\"`. Store this for subsequent commands.\n\n### Step 2: Gather Initial Information\n\n```bash\nSESSION=\"\u003Csession_id>\"\n\n# List all threads\ngdb-cli threads -s $SESSION\n\n# Get backtrace (with local variables)\ngdb-cli bt -s $SESSION --full\n\n# Get registers\ngdb-cli registers -s $SESSION\n```\n\n### Step 3: Correlate Source Code (CRITICAL)\n\nFor each frame in the backtrace:\n1. **Extract frame info**: `{file}:{line} in {function}`\n2. **Read source context**: Get ±20 lines around the crash point\n3. **Get local variables**: `gdb-cli locals-cmd -s $SESSION --frame \u003CN>`\n4. **Analyze**: Correlate code logic with variable values\n\n**Example correlation:**\n```\nFrame #0: process_data() at src\u002Fworker.c:87\nSource code shows:\n  85: Node* node = get_node(id);\n  86: if (node == NULL) return;\n  87: node->data = value;  \u003C- Crash here\n\nVariables show:\n  node = 0x0 (NULL)\n\nAnalysis: The NULL check on line 86 didn't catch the issue.\n```\n\n### Step 4: Deep Investigation\n\n```bash\n# Examine variables\ngdb-cli eval-cmd -s $SESSION \"variable_name\"\ngdb-cli eval-cmd -s $SESSION \"ptr->field\"\ngdb-cli ptype -s $SESSION \"struct_name\"\n\n# Memory inspection\ngdb-cli memory -s $SESSION \"0x7fffffffe000\" --size 64\n\n# Disassembly\ngdb-cli disasm -s $SESSION --count 20\n\n# Check all threads (for deadlock analysis)\ngdb-cli thread-apply -s $SESSION bt --all\n\n# View shared libraries\ngdb-cli sharedlibs -s $SESSION\n```\n\n### Step 5: Session Management\n\n```bash\n# List active sessions\ngdb-cli sessions\n\n# Check session status\ngdb-cli status -s $SESSION\n\n# Stop session (cleanup)\ngdb-cli stop -s $SESSION\n```\n\n## Common Debugging Patterns\n\n### Pattern: Null Pointer Dereference\n\n**Indicators:**\n- Crash on memory access instruction\n- Pointer variable is 0x0\n\n**Investigation:**\n```bash\ngdb-cli registers -s $SESSION  # Check RIP\ngdb-cli eval-cmd -s $SESSION \"ptr\"  # Check pointer value\n```\n\n### Pattern: Deadlock\n\n**Indicators:**\n- Multiple threads stuck in lock functions\n- `pthread_mutex_lock` in backtrace\n\n**Investigation:**\n```bash\ngdb-cli thread-apply -s $SESSION bt --all\n# Look for circular wait patterns\n```\n\n### Pattern: Memory Corruption\n\n**Indicators:**\n- Crash in malloc\u002Ffree\n- Garbage values in variables\n\n**Investigation:**\n```bash\ngdb-cli memory -s $SESSION \"&variable\" --size 128\ngdb-cli registers -s $SESSION\n```\n\n## Examples\n\n### Example 1: Core Dump Analysis\n\n```bash\n# Load core dump\ngdb-cli load --binary .\u002Fmyapp --core \u002Ftmp\u002Fcore.1234\n\n# Get crash location\ngdb-cli bt -s a1b2c3 --full\n\n# Examine crash frame\ngdb-cli locals-cmd -s a1b2c3 --frame 0\n```\n\n### Example 2: Live Process Debugging\n\n```bash\n# Attach to stuck server\ngdb-cli attach --pid 12345\n\n# Check all threads\ngdb-cli threads -s b2c3d4\n\n# Get all backtraces\ngdb-cli thread-apply -s b2c3d4 bt --all\n```\n\n## Best Practices\n\n- Always read source code before drawing conclusions from variable values\n- Use `--range` for pagination on large thread counts or deep backtraces\n- Use `ptype` to understand complex data structures before examining values\n- Check all threads for multi-threaded issues\n- Cross-reference types with source code definitions\n\n## Security & Safety Notes\n\n- This skill requires GDB access to processes and core dumps\n- Attaching to processes may require appropriate permissions (sudo, ptrace_scope)\n- Core dumps may contain sensitive data - handle with care\n- Only debug processes you have authorization to analyze\n\n## Related Skills\n\n- `@systematic-debugging` - General debugging methodology\n- `@test-driven-development` - Write tests before implementation\n\n## Links\n\n- **Repository**: https:\u002F\u002Fgithub.com\u002FCerdore\u002Fgdb-cli\n- **PyPI**: https:\u002F\u002Fpypi.org\u002Fproject\u002Fgdb-cli\u002F\n- **Documentation**: https:\u002F\u002Fgithub.com\u002FCerdore\u002Fgdb-cli#readme\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# GDB Debugging Assistant\n\n## Overview\n\nA GDB debugging skill designed for AI agents. Combines **source code analysis** with **runtime state inspection** using gdb-cli to provide intelligent debugging assistance for C\u002FC++ programs.\n\n## When to Use This Skill\n\n- Analyze core dumps or crash dumps\n- Debug running processes with GDB attach\n- Investigate crashes, deadlocks, or memory issues\n- Get intelligent debugging assistance with source code context\n- Debug multi-threaded applications\n\n## Do Not Use This Skill When\n\n- The task is unrelated to C\u002FC++ debugging\n- The user needs general-purpose assistance without debugging\n- No GDB is available (GDB 9.0+ with Python support required)\n\n## Prerequisites\n\n```bash\n# Install gdb-cli\npip install gdb-cli\n\n# Or from GitHub\npip install git+https:\u002F\u002Fgithub.com\u002FCerdore\u002Fgdb-cli.git\n\n# Verify GDB has Python support\ngdb -nx -q -batch -ex \"python print('OK')\"\n```\n\n**Requirements:**\n- Python 3.6.8+\n- GDB 9.0+ with Python support enabled\n- Linux OS\n\n## How It Works\n\n### Step 1: Initialize Debug Session\n\n**For core dump analysis:**\n```bash\ngdb-cli load --binary \u003Cbinary_path> --core \u003Ccore_path> [--gdb-path \u003Cgdb_path>]\n```\n\n**For live process debugging:**\n```bash\ngdb-cli attach --pid \u003Cpid> [--binary \u003Cbinary_path>]\n```\n\n**Output:** A session_id like `\"session_id\": \"a1b2c3\"`. Store this for subsequent commands.\n\n### Step 2: Gather Initial Information\n\n```bash\nSESSION=\"\u003Csession_id>\"\n\n# List all threads\ngdb-cli threads -s $SESSION\n\n# Get backtrace (with local variables)\ngdb-cli bt -s $SESSION --full\n\n# Get registers\ngdb-cli registers -s $SESSION\n```\n\n### Step 3: Correlate Source Code (CRITICAL)\n\nFor each frame in the backtrace:\n1. **Extract frame info**: `{file}:{line} in {function}`\n2. **Read source context**: Get ±20 lines around the crash point\n3. **Get local variables**: `gdb-cli locals-cmd -s $SESSION --frame \u003CN>`\n4. **Analyze**: Correlate code logic with variable values\n\n**Example correlation:**\n```\nFrame #0: process_data() at src\u002Fworker.c:87\nSource code shows:\n  85: Node* node = get_node(id);\n  86: if (node == NULL) return;\n  87: node->data = value;  \u003C- Crash here\n\nVariables show:\n  node = 0x0 (NULL)\n\nAnalysis: The NULL check on line 86 didn't catch the issue.\n```\n\n### Step 4: Deep Investigation\n\n```bash\n# Examine variables\ngdb-cli eval-cmd -s $SESSION \"variable_name\"\ngdb-cli eval-cmd -s $SESSION \"ptr->field\"\ngdb-cli ptype -s $SESSION \"struct_name\"\n\n# Memory inspection\ngdb-cli memory -s $SESSION \"0x7fffffffe000\" --size 64\n\n# Disassembly\ngdb-cli disasm -s $SESSION --count 20\n\n# Check all threads (for deadlock analysis)\ngdb-cli thread-apply -s $SESSION bt --all\n\n# View shared libraries\ngdb-cli sharedlibs -s $SESSION\n```\n\n### Step 5: Session Management\n\n```bash\n# List active sessions\ngdb-cli sessions\n\n# Check session status\ngdb-cli status -s $SESSION\n\n# Stop session (cleanup)\ngdb-cli stop -s $SESSION\n```\n\n## Common Debugging Patterns\n\n### Pattern: Null Pointer Dereference\n\n**Indicators:**\n- Crash on memory access instruction\n- Pointer variable is 0x0\n\n**Investigation:**\n```bash\ngdb-cli registers -s $SESSION  # Check RIP\ngdb-cli eval-cmd -s $SESSION \"ptr\"  # Check pointer value\n```\n\n### Pattern: Deadlock\n\n**Indicators:**\n- Multiple threads stuck in lock functions\n- `pthread_mutex_lock` in backtrace\n\n**Investigation:**\n```bash\ngdb-cli thread-apply -s $SESSION bt --all\n# Look for circular wait patterns\n```\n\n### Pattern: Memory Corruption\n\n**Indicators:**\n- Crash in malloc\u002Ffree\n- Garbage values in variables\n\n**Investigation:**\n```bash\ngdb-cli memory -s $SESSION \"&variable\" --size 128\ngdb-cli registers -s $SESSION\n```\n\n## Examples\n\n### Example 1: Core Dump Analysis\n\n```bash\n# Load core dump\ngdb-cli load --binary .\u002Fmyapp --core \u002Ftmp\u002Fcore.1234\n\n# Get crash location\ngdb-cli bt -s a1b2c3 --full\n\n# Examine crash frame\ngdb-cli locals-cmd -s a1b2c3 --frame 0\n```\n\n### Example 2: Live Process Debugging\n\n```bash\n# Attach to stuck server\ngdb-cli attach --pid 12345\n\n# Check all threads\ngdb-cli threads -s b2c3d4\n\n# Get all backtraces\ngdb-cli thread-apply -s b2c3d4 bt --all\n```\n\n## Best Practices\n\n- Always read source code before drawing conclusions from variable values\n- Use `--range` for pagination on large thread counts or deep backtraces\n- Use `ptype` to understand complex data structures before examining values\n- Check all threads for multi-threaded issues\n- Cross-reference types with source code definitions\n\n## Security & Safety Notes\n\n- This skill requires GDB access to processes and core dumps\n- Attaching to processes may require appropriate permissions (sudo, ptrace_scope)\n- Core dumps may contain sensitive data - handle with care\n- Only debug processes you have authorization to analyze\n\n## Related Skills\n\n- `@systematic-debugging` - General debugging methodology\n- `@test-driven-development` - Write tests before implementation\n\n## Links\n\n- **Repository**: https:\u002F\u002Fgithub.com\u002FCerdore\u002Fgdb-cli\n- **PyPI**: https:\u002F\u002Fpypi.org\u002Fproject\u002Fgdb-cli\u002F\n- **Documentation**: https:\u002F\u002Fgithub.com\u002FCerdore\u002Fgdb-cli#readme\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"tags":25,"tools":32,"author":38,"source":39,"category":40,"date_added":41,"description":7},"critical",[26,27,28,29,30,31],"debugging","gdb","core-dump","crash-analysis","c++","c",[33,34,35,36,37],"claude-code","cursor","gemini-cli","codex-cli","antigravity","Cerdore","community","development","2026-03-22","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fgdb-cli",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill gdb-cli",{"tool":56,"command":57},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill gdb-cli",{"tool":59,"command":60},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill gdb-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgdb-cli\u002FSKILL.md",true,[],[65,72,77,84,91,98],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":73,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]