Wenyong Huang

@ssssssyy0112 touch_pages is needed for the native stack boundary check with hardware trap mechanism, if it doesn't work for you, could you try disabling it with `cmake -DWAMR_DISABLE_HW_BOUND_CHECK=1`: https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/build_wamr.md#disable-native-stack-boundary-check-with-hardware-trap And...

Hi, sorry for the typo, please had better use `cmake -DWAMR_DISABLE_STACK_HW_BOUND_CHECK=1` to build iwasm, and use `wamrc --stack-bounds-checks=1` to compile the wasm file. This only disables the native stack boundary...

@erxiaozhou thanks for spotting the issue, it was fixed with https://github.com/bytecodealliance/wasm-micro-runtime/pull/3101, please pull the latest code to test again.

Close this issue since it had been resolved.

Hi, "HashMap find elem failed: map or key is NULL" should be not an error, could you please try patch below: ```diff diff --git a/core/iwasm/common/wasm_shared_memory.c b/core/iwasm/common/wasm_shared_memory.c index 70e84a37..f33dc043 100644 ---...

Do you rebuild iwasm? If the warning keeps showing, could you help debug iwasm, e.g. add break point at https://github.com/bytecodealliance/wasm-micro-runtime/blob/8b37048823677d9229b7458b064a515b19744c9c/core/shared/utils/bh_hashmap.c#L134 and check which function is calling bh_hash_map_find?

Hi, it seems that wasi-sdk doesn't support posix semaphore APIs so the compiled wasm app imports sem_xxx APIs, there may be two ways: one is to use WAMR lib-pthread instead,...

Hi, I am afraid I have no idea about the roadmap of wasi-sdk, maybe you can open issue in wasi-sdk's community.

If to use the builtin sem_xxx apis, you should enable the lib-pthread library, but it seems that you also enable the lib-wasi-threads? I think you had better just pick one,...

Hi, I tested the result of the gcc native (gcc -O3 -o test main, and then ./test), it also creates a 169-byte file. It is confusing whether we should comply...