Userzxcvbvnm

> @Userzxcvbvnm In which file is error coming? WasmEdge does not print "Access mode: O_TRUNC"

It is a file with random generated string as the content "asadsdwedfwe34r34r"

Thanks for your reply!

I tried to compile it with `./wasi-sdk-21.0/bin/clang --target=wasm32-unkown-wasi --sysroot=./wasi-sdk-21.0/share/wasi-sysroot test.c -o test.wasm` (Before run the Wasm file, softfile_1 exists and is a softlink file points to subdir_1/subdir_1/subfile_2.) wasmedge --dir=. test.wasm...

> **PROBLEM** I tried to compile with above command, but I compiled it with **wasi-sdk-24.0**. It is showing the same error which you proposed! > > With Wasmedge  With...

Using wasi-sdk21 or wasi-sdk24, We got the same result: (1)wasmtime command:`wasmtime run --dir=. test.wasm` (Should use --dir=. to set the pre-opened directory for wasmtime, rather than using 'wasmtime test.wasm') result:...

This may be related to https://github.com/wasmerio/wasmer/issues/4245

We checked different OS permission with different openstyle, and found that wasmer is different from other WASM runtimes, including wasmtime, WAMR and WasmEdge. The behavior of other WASM runtimes is...

Thanks for your reply! I reproduce this with Linux native code (`gcc test.c -o test`, `./test`) and Linux native has the same behavior with WAMR and WasmEdge. I'm not sure...

Thanks for your reply! As you suggested, I'll open a bug with WASI to figure out the correct behavior.