Q1IQ

Thank you for your response! I believe it is necessary for the runtime to handle this. (1) WebAssembly Specification Requirements: The WebAssembly specification explicitly defines how the runtime should execute...

Thanks for the explanation. I understand that the WASM is invalid, but the difference between debug and release behaviors still seems unintended. Ideally, both builds should surface the same failure...

The CMake options I used for the build, FYI: ``` cmake -DCMAKE_BUILD_TYPE=Debug \ -DCMAKE_C_COMPILER=gcc \ -DCMAKE_CXX_COMPILER=g++ \ -DCMAKE_C_FLAGS="-g -O1 -fno-omit-frame-pointer" \ -DCMAKE_CXX_FLAGS="-g -O1 -fno-omit-frame-pointer" \ -DCMAKE_EXE_LINKER_FLAGS="-fsanitize=address -fno-sanitize=leak" \ -DWAMR_BUILD_INTERP=1 \...

> IIUC, it is only reproducible with a debug build. With a release build, an exception will be raised, such as: `Exception: out of bounds table access`. Therefore, this is...

The WASM file has already been uploaded.