From cb88edf0bfdc2ce6bfbe3b4e0463a4c2dc5d2230 Mon Sep 17 00:00:00 2001
From: Takashi Kokubun <takashikkbn@gmail.com>
Date: Tue, 13 May 2025 17:03:39 -0700
Subject: Set WASMTIME_BACKTRACE_DETAILS=1 for WASM basictest

https://github.com/ruby/ruby/actions/runs/15008767265/job/42173424631
"error while executing at wasm backtrace" doesn't have meaningful
symbols. We can't debug this from just looking at the "[BUG] Cannot
malloc during GC" message.

As suggested by the error message, this commit sets WASMTIME_BACKTRACE_DETAILS=1.
Let me see if this improves the backtrace.
---
 .github/workflows/wasm.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.github/workflows/wasm.yml b/.github/workflows/wasm.yml
index 047288cb8d..88ea7bd76c 100644
--- a/.github/workflows/wasm.yml
+++ b/.github/workflows/wasm.yml
@@ -152,6 +152,8 @@ jobs:
 
       - name: Run basictest
         run: wasmtime run ./../build/miniruby --mapdir /::./ -- basictest/test.rb
+        env:
+          WASMTIME_BACKTRACE_DETAILS: '1'
         working-directory: src
 
       - name: Run bootstraptest (no thread)
-- 
cgit v1.2.3