rspack-debugging

Debug Rspack crashes and deadlocks using LLDB backtrace capture.

86|1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/rstackjs/agent-skills --skill rspack-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rspack-debugging
Source: https://github.com/rstackjs/agent-skills/tree/main/skills/rspack-debugging
Command: npx skills add https://github.com/rstackjs/agent-skills --skill rspack-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Rspack users and developers often encounter crashes, segmentation faults, or deadlocks during builds. This Skill provides a structured approach using LLDB to capture backtraces, identify failing threads, and guide remediation.

Core Features & Use Cases

  • LLDB-based backtrace collection for Rspack processes to diagnose crashes and hangs.
  • Guided workflows for common scenarios (crash during development server, crash during build, attached to stuck process, core dump analysis).
  • Artifact preservation: save backtraces and logs to project files for later analysis.

Quick Start

  • Install LLDB if needed (macOS: xcode-select --install; Linux: apt-get install lldb).
  • Run the automatic setup script to install debug dependencies: node ${CLAUDE_PLUGIN_ROOT}/skills/debugging/scripts/setup_debug_deps.cjs
  • Start the Rspack build under LLDB batch mode to collect backtraces, for example: lldb --batch -o "run" -k "thread backtrace all" -k "quit" -- node node_modules/@rspack/cli/bin/rspack.js build
  • Save the backtrace outputs to a file in your project, e.g., debug_artifacts/backtrace_build.txt

Frequently Asked Questions about rspack-debugging

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

FAQPage Schema
How do I capture a backtrace when Rspack crashes or hangs during a build?

Use LLDB to capture backtraces by running your Rspack build under LLDB batch mode with the command: lldb --batch -o "run" -k "thread backtrace all" -k "quit" -- node node_modules/@rspack/cli/bin/rspack.js build. Save the output to a file in your project for analysis.

What tools do I need to debug Rspack crashes and deadlocks?

You need LLDB installed (macOS: xcode-select --install; Linux: apt-get install lldb) and debug dependencies for Rspack. Run the setup script at node ${CLAUDE_PLUGIN_ROOT}/skills/debugging/scripts/setup_debug_deps.cjs to configure your environment.

Can I debug a Rspack process that's already stuck or hung?

Yes. LLDB supports attaching to running processes to capture backtraces from stuck Rspack builds and deadlocks. The Skill provides guided workflows for this scenario, enabling you to inspect thread states without restarting the build.

How do I analyze a core dump from a Rspack crash?

LLDB can load and analyze core dumps to extract backtraces and identify the failing code path. The Skill includes a guided workflow for core dump analysis that structures the remediation process after capturing the dump.

Where should I store backtrace outputs from debugging sessions?

Save backtraces and logs to a project directory like debug_artifacts/ (e.g., debug_artifacts/backtrace_build.txt) for later analysis, version control integration, and team collaboration on crash remediation.