erhe-cpp-debugging

Debug C++ crashes and deadlocks in the erhe project using lldb or Visual Studio MCP server.

896|86|Updated May 1, 2021
One-click install
npx skills add https://github.com/tksuoran/erhe --skill erhe-cpp-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: erhe-cpp-debugging
Source: https://github.com/tksuoran/erhe/tree/main/.claude/skills/erhe-cpp-debugging
Command: npx skills add https://github.com/tksuoran/erhe --skill erhe-cpp-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the problem of diagnosing and debugging C++ crashes, aborts, exceptions, hangs, and deadlocks in the erhe project, providing detailed callstacks and live variable values to facilitate precise troubleshooting.

Core Features & Use Cases

  • Real-time Debugging: Access live callstacks and variable values during runtime for detailed diagnostics.
  • Platform-specific Solutions: Supports macOS (lldb with Python SB API) and Windows (Visual Studio MCP server).
  • Use Case: When an "erhe editor.exe" crashes with a non-zero exit code or an unhandled exception, use this skill to reproduce the failure and get a real callstack and variable values for diagnosis.

Quick Start

Reproduce a crash or deadlock and initiate debugging by executing 'lldb' command followed by script imports and configurations for the specific platform.

Frequently Asked Questions about erhe-cpp-debugging

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

FAQPage Schema
How do I debug a C++ crash or deadlock with live variable values?

Use source-level C++ debugging to reproduce crashes or deadlocks and inspect live callstacks and variable values. This provides detailed runtime diagnostics to identify the exact cause of aborts, exceptions, or hangs.

Can I use lldb for C++ debugging on macOS and Linux?

Yes, lldb is utilized for C++ debugging on macOS and Linux. It leverages the Python SB API to provide source-level visibility into callstacks and variable values during crash diagnosis.

Does C++ debugging work with Visual Studio MCP server on Windows?

Yes, C++ debugging on Windows is handled through the Visual Studio MCP server. This integration enables source-level reproduction and diagnosis of unhandled exceptions and deadlocks.

What is the best way to diagnose hangs and deadlocks in C++?

The best way to diagnose hangs and deadlocks in C++ is to reproduce the failure under a source-level debugger. This captures real callstacks across threads and live variable states to pinpoint the synchronization issue.

How do I get a real callstack when my C++ editor.exe crashes with a non-zero exit code?

To get a real callstack when a C++ editor.exe crashes with a non-zero exit code, reproduce the failure using source-level debugging. This captures the exact callstack and live variable values at the moment of the crash.