AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Rspack Debugging

skill-rstackjs-agent-skills-rspack-debugging · by rstackjs

Helps Rspack users and developers debug crashes or deadlocks/hangs in the Rspack build process using LLDB. Use this Skill when users encounter "Segmentation fault" errors during Rspack builds or when the build progress gets stuck.

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-rstackjs-agent-skills-rspack-debugging

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-rstackjs-agent-skills-rspack-debugging)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Rspack Debugging? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Rspack Debugging

Overview

This Skill guides you on how to capture the underlying crash state of Rspack (which is based on Rust). By using the LLDB debugger and Rspack packages with debug symbols, we can obtain detailed stack backtraces, which are crucial for pinpointing issues. The guides focus on non-interactive, automated debugging to easily capture backtraces.

Preparation

Before starting, please ensure your environment meets the requirements.

  1. Install LLDB: You must install the LLDB debugger.
  • macOS: Run xcode-select --install
  • Linux: Install the lldb package (e.g., apt-get install lldb)
  • Detailed guide: [references/lldb.md](references/lldb.md)
  1. Replace Debug Packages:

Production packages like @rspack/core have debug symbols stripped. They must be replaced with the @rspack-debug/* series packages to see useful stack information.

Automatic Replacement Script:

``bash node ${CLAUDE_PLUGIN_ROOT}/skills/debugging/scripts/setup_debug_deps.cjs ``

Running the above script will automatically add pnpm.overrides configuration to package.json, pointing Rspack packages to their corresponding Debug versions. Afterwards, please be sure to run pnpm install to update dependencies.

Debugging Workflows

Identify your specific scenario and follow the corresponding linked guide.

Detailed Guides

Detailed Guides

Guide A: Crash during HMR

Scenario: Stable Crash/Deadlock during DevServer HMR. [Read Guide: references/guideahmrcrash.md](references/guideahmrcrash.md)

Guide B: Crash during Build

Scenario: Stable Crash/Deadlock during Build (or Unstable Build Crash that is frequent enough). [Read Guide: references/guidebbuildcrash.md](references/guidebbuildcrash.md)

Guide C: Attach to Stuck Process

Scenario: Unstable Deadlock during Build (happens randomly). [Read Guide: references/guidecattachtostuckprocess.md](references/guidecattachtostuckprocess.md)

Guide D: Coredump Analysis (Dev)

Scenario: Unstable Crash during DevServer HMR (hard to catch interactively). [Read Guide: references/guidedcoredumpanalysisdev.md](references/guidedcoredumpanalysisdev.md)

Guide E: Coredump Analysis (Build)

Scenario: Unstable Crash during Build. [Read Guide: references/guideecoredumpanalysisbuild.md](references/guideecoredumpanalysisbuild.md)

Guide F: Async Deadlock Identification

Scenario: Unstable Async Deadlock. Main thread stuck in uv_run. [Read Guide: references/guidefasyncdeadlock.md](references/guidefasyncdeadlock.md)

Saving Debug Artifacts

Critical Instruction for Agents: When you successfully obtain a backtrace or a tracing log, you MUST save it to a local file in the user's project directory so it is preserved after the session.

  1. Create Directory: Ensure a directory named debug_artifacts exists in the project root.
  2. Save Backtraces: Write the full output of thread backtrace all to debug_artifacts/backtrace_.txt.
  3. Save Tracing Logs: (Only if using Tracing Skill)

Environment Restoration

After debugging is complete, restore your package.json to use production packages:

node ${CLAUDE_PLUGIN_ROOT}/skills/debugging/scripts/setup_debug_deps.cjs --restore
pnpm install

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills