-
Notifications
You must be signed in to change notification settings - Fork 793
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to get the file discriptor? #4753
Comments
It seems wasmer could ont open any file, whether native and other runtimes could. |
@Userzxcvbvnm could you please test your use case with #4730? since I believe this is a duplicate of #4724. |
I tried my test case with the wasmer of commit 4730, but failed again with the same output I mentioned.
|
Thanks for testing. I'll investigate. |
I can confirm your provided example, now works using the latest commit of #4730. |
Thanks for your reply and commit! |
Describe the bug
Fail to get the file descriptor, while other Wasm runtimes and native could get it successfully.
Steps to reproduce
The c file is :
(1)compile to Wasm:
./wasi-sdk-21.0/bin/clang --target=wasm32-unkown-wasi --sysroot=./wasi-sdk-21.0/share/wasi-sysroot read.c -o read.wasm
(2)compile to native code:
gcc read.c -o read
(3)Running wasm:
wasmer run --dir=. read.wasm
(4)Running native binaries
./read
Expected behavior
Output:
Get file descriptor of file ./hello.txt succeed!
And this is the output of native and other Wasm runtimes, such as wasmtime.
Actual behavior
wasmer prints:
Get file descriptor of file ./hello.txt failed!
Additional context
Ubuntu 20.04
wasmer-4.3.1
The text was updated successfully, but these errors were encountered: