การแก้ไขข้อบกพร่องของโมดูล WebAssembly

Ever wondered how to peek inside your WebAssembly code while it runs? Debugging WASM lets you find and fix issues in your high-performance modules.

It's a bit different from debugging pure JavaScript, but modern browser developer tools offer powerful capabilities to help you out.

Your browser's developer tools are your best friend for WASM debugging. In Chrome, open DevTools (F12 or Cmd+Option+I).

• Navigate to the Sources tab.
• Look for your WASM module in the file tree, often under wasm:// or similar.
• Without source maps, you'll see raw WebAssembly text format – which is very hard to read!

Debugging raw WebAssembly text is incredibly tough! Source maps are special files that link the compiled WASM code back to your original C, C++, or Rust source code.

When present, your browser can display your original source files, allowing you to debug them directly, just like JavaScript.

When compiling Rust to WASM, tools like wasm-pack can automatically generate source maps. The key is to compile in debug mode.

A simple Rust function that adds one to a number:

Let's see how a browser loads a WASM module. When compiled with source maps (e.g., wasm-pack build --target web --dev), the browser uses them to show your original Rust/C/C++ files in the Sources tab.

Here's how JavaScript loads a tiny, conceptual WASM module:

Just like JavaScript, you can set breakpoints directly in your original C/C++/Rust source files shown in the Sources tab of your browser's DevTools.

• Click on the line number in the gutter where you want to pause execution.
• When your WASM code executes that line, the browser will pause, letting you inspect variables and the call stack.

When execution pauses at a breakpoint, you gain powerful insights:

• Scope pane: View local variables and function arguments, often with their original names if source maps are good.
• Memory Inspector: Use the dedicated 'Memory' tab or right-click a memory address to inspect WASM's linear memory buffer.
• Call Stack pane: See the sequence of function calls that led to the current point, including both JavaScript and WASM frames.

Once paused at a breakpoint, use the debugger controls to navigate your code line by line:

• Step Over (F10): Execute the current line and move to the next.
• Step Into (F11): Dive into a function call on the current line.
• Step Out (Shift+F11): Finish executing the current function and return to where it was called.
• Resume (F8): Continue execution until the next breakpoint or the program ends.

Often, bugs occur at the boundary where JavaScript calls WASM functions or vice-versa. Set breakpoints in both your JavaScript and WASM code.

You can step seamlessly between JS and WASM execution frames in the DevTools call stack, making it easy to trace data flow and identify issues in the interop layer.

Today, you learned how to leverage browser developer tools to debug your WebAssembly applications. We covered:

• Using source maps to see original source code.
• Setting breakpoints and stepping through execution.
• Inspecting variables, memory, and the call stack.
• Debugging interactions between JavaScript and WASM.

Mastering these techniques is crucial for building robust and performant WASM applications. Keep practicing!