debug-lldb

Capture thread backtraces from live processes using LLDB and GDB.

131|13|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/regenrek/agent-skills --skill debug-lldb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-lldb
Source: https://github.com/regenrek/agent-skills/tree/main/skills/debug-lldb
Command: npx skills add https://github.com/regenrek/agent-skills --skill debug-lldb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Quickly diagnose unresponsive applications by capturing and analyzing thread backtraces from live processes across macOS, Linux, and Windows.

Core Features & Use Cases

  • Cross-platform backtrace collection: LLDB on macOS and GDB on Linux/Windows to capture thread stacks.
  • Deterministic troubleshooting workflow: Use the bundled scripts to collect repeated samples for triage.
  • Contextual triage guidance: Reference patterns to classify stalls, deadlocks, and busy loops.
  • Example: If an app UI freezes under heavy I/O, collect multiple samples to identify the blocking thread.

Quick Start

Run the guided workflow: identify the target process PID and execute the provided script to capture stack traces, then consult references/triage.md for interpretation.

Frequently Asked Questions about debug-lldb

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

FAQPage Schema
How do I capture thread backtraces from a running process to diagnose hangs?

Capture thread backtraces from a live process by running the bundled collect_stacks.sh script against the target PID, which gathers multiple stack samples to triage unresponsive application stalls. It works across macOS using LLDB and Linux or Windows using GDB.

What is the best way to triage a busy loop or deadlock from a live process stack trace?

Triage a busy loop or deadlock by collecting repeated thread backtrace samples and comparing them against bundled reference patterns in triage.md to classify the stall type. Repeated samples reveal threads stuck in identical frames, indicating a blocking operation or active spin.

Can I use LLDB to collect stack traces on macOS and GDB on Linux for the same troubleshooting workflow?

Yes, you can use LLDB on macOS and GDB on Linux or Windows for the same deterministic troubleshooting workflow. The Skill applies a cross-platform backtrace collection workflow to capture thread stacks from live processes regardless of the operating system.

How do I identify which thread is causing a UI freeze under heavy I/O load?

Identify the thread causing a UI freeze by executing the provided script to capture multiple thread backtrace samples during the stall, then consult the contextual triage guidance to pinpoint the blocking thread responsible for the unresponsive behavior.

Do I need any external dependencies to collect and analyze live thread backtraces?

No external dependencies are required to collect and analyze live thread backtraces. The Skill bundles the necessary collection script and a references directory with triage patterns, requiring only the native platform debugger like LLDB or GDB installed on the system.

Why should I collect multiple stack samples instead of a single backtrace to debug an unresponsive app?

Collect multiple stack samples instead of a single backtrace to distinguish a permanent hang from a temporary stall. Repeated sampling allows you to triage results against reference patterns, revealing whether threads are deadlocked, spinning in a busy loop, or waiting on I/O.