ckb-standalone-debugger

Coordinate offline CKB debugging workflows across a Rust monorepo workspace.

22|22|Updated Sep 10, 2019

Search Tags:#debugging #monorepo #rust #wasm #gdb #flamegraph #ckb

Ready to run

npx skills add https://github.com/nervosnetwork/ckb-standalone-debugger --skill ckb-standalone-debugger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ckb-standalone-debugger
Source: https://github.com/nervosnetwork/ckb-standalone-debugger/tree/main
Command: npx skills add https://github.com/nervosnetwork/ckb-standalone-debugger --skill ckb-standalone-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers who work on the ckb-standalone-debugger monorepo to coordinate offline CKB contract execution, mock transaction debugging, GDB sessions, flamegraph and coverage analysis, or WASM support.

Core Features & Use Cases

Supports offline contract execution workflows across the workspace crates (ckb-debugger, ckb-vm-pprof, ckb-vm-signal-profiler, etc.).
Enables mock-transaction debugging, GDB-based debugging sessions, flamegraph generation, and coverage analysis workflows.
Provides WASM usage considerations across native and browser-like environments for browser/WASM targets.

Quick Start

Clone the repository and run cargo build to compile all crates, then try a sample workflow with a mocked transaction.

Frequently Asked Questions about ckb-standalone-debugger

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

FAQPage Schema

How do I debug CKB smart contracts offline in a Rust monorepo?▼

To debug CKB contracts offline in a Rust monorepo, clone the repository and run cargo build to compile all crates, then execute a sample workflow with a mocked transaction to test contract behavior.

Can I use GDB and generate flamegraphs for offline CKB contract execution?▼

Yes, offline CKB contract execution supports GDB-based debugging sessions and flamegraph generation, enabling you to step through code and visualize performance profiles across workspace crates.

Does the CKB debugger support WASM testing in browser-like environments?▼

WASM support testing is included for browser-like environments, providing specific usage considerations for executing and validating CKB contracts compiled to WASM targets.

What is the best way to run mock transaction debugging for CKB contracts?▼

Mock transaction debugging is handled by executing mocked transactions within the standalone workspace, allowing you to isolate and validate contract logic without connecting to a live network.

How does coverage analysis work during offline CKB contract execution?▼

Coverage analysis workflows operate during offline contract execution by profiling the running code across the workspace crates, generating metrics that show which execution paths were tested.

What are the limitations of using a standalone debugger for CKB contracts?▼

As a standalone tool, it coordinates offline execution and mock debugging but does not connect to a live blockchain network, meaning it cannot validate real-time node interactions or live chain state.