Lîm Tsú-thuàn

Issue will be open if still having thing todo, WasmEdge haven’t go into stable mode, which mean we won’t port bug fix back to older version. Therefore, I believe there...

Note: need bisect to find which commit introduce the problem in 0.13.5.

https://github.com/WasmEdge/WasmEdge/blob/master/lib/executor/engine/engine.cpp

@XinyuShe Do you still remember the wasmtime version you using? I get some interesting result: The behavior of wasmtime is different from original report. ```shell $ wasmtime run --invoke main...

Probably due to system difference, I use macOS 14.1.1

Interpreter mode remains fine, AOT.

Does the issue complete?

WasmEdge has no JIT mode yet, but interpreter mode, though JIT is recent plan.

I use - WasmEdge 43ec1fdb0089d4f95c908d86b5ccf8f1199aef21 - wasmtime 18.0.2 (90db6e99f 2024-02-28) then do ``` $ wasmtime fd_sync.wasm $ echo $? 8 $ wasmedge fd_sync.wasm $ echo $? 8 ``` I'm wondering...

Could you provide link to the image?