mvx_wasm_debug

Analyze MultiversX WASM binaries for size and panic debugging.

12|5|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/multiversx/mx-ai-skills --skill mvx-wasm-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mvx_wasm_debug
Source: https://github.com/multiversx/mx-ai-skills/tree/main/antigravity/skills/mvx_wasm_debug
Command: npx skills add https://github.com/multiversx/mx-ai-skills --skill mvx-wasm-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers analyze compiled WebAssembly (WASM) binaries for MultiversX smart contracts, enabling them to understand binary size, debug panics, and map WASM instructions back to source code.

Core Features & Use Cases

  • Binary Size Analysis: Identify components contributing to WASM file size using tools like Twiggy.
  • Panic Analysis: Understand and debug contract execution failures and abort messages.
  • DWARF Debugging: Leverage debug symbols to map WASM code to Rust source lines for in-depth debugging.
  • Use Case: When a MultiversX smart contract unexpectedly traps during execution, this skill can be used to analyze the WASM binary, inspect panic messages, and use DWARF symbols to pinpoint the exact Rust source line causing the issue.

Quick Start

Analyze the size of the 'output.wasm' file using the twiggy top command.

Frequently Asked Questions about mvx_wasm_debug

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

FAQPage Schema
How do I debug a WASM binary that traps during MultiversX smart contract execution?

Debug a WASM binary by analyzing the MultiversX smart contract failure, inspecting abort messages, and using DWARF symbols to pinpoint the exact Rust source line causing the execution trap.

What is the best way to analyze WASM binary size for MultiversX smart contracts?

Analyze WASM binary size by running the twiggy top command on the output.wasm file, which identifies the specific components and code structures contributing to the overall smart contract file size.

Can I map WebAssembly instructions back to Rust source lines using DWARF debugging?

DWARF debugging maps WebAssembly instructions to Rust source lines by leveraging debug symbols generated during the build process, enabling in-depth analysis of MultiversX smart contract execution failures.

Do I need special build tools to generate debug symbols for MultiversX WASM analysis?

Generating debug symbols for MultiversX WASM analysis requires WASM build tools configured to produce debug symbols, which are necessary to map the compiled binary instructions back to the original source code.

Why does my MultiversX smart contract panic and how can I understand the abort message?

Panic analysis examines MultiversX smart contract abort messages to understand execution failures, using DWARF symbols to trace the panic back to the specific Rust source line triggering the abort.

What limitations exist when debugging WebAssembly binaries without DWARF symbols?

Debugging WebAssembly binaries without DWARF symbols limits analysis to binary-level inspection and abort messages, preventing the mapping of WASM instructions back to the exact Rust source lines required for in-depth debugging.