Skip to content
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

Unexpected behavior when calling open #246

Open
jlb6740 opened this issue Jun 8, 2023 · 1 comment
Open

Unexpected behavior when calling open #246

jlb6740 opened this issue Jun 8, 2023 · 1 comment

Comments

@jlb6740
Copy link
Collaborator

jlb6740 commented Jun 8, 2023

#238 ran into this, but ackermann was made working again by avoiding the problem. The issue is different behavior was seen from open
when comparing the native engine vs the wasm engine and calling open:

int fd = open(path, 0);

The Wasm engine seemed to not attempt the open (at least when looking at strace data) while the the native engine opened the file just fine. Moreover when compiling the Wasm without sightglass imports so that we can run in standalone Wasmtime, the above statement does work. So we are seeing incorrect behavior with wasmtime usage in sightglass compared to wasmtime standalone or native usage in sightglass. Since #238 was closed due to ackermann working again, wanted to record that the underlying issue is still there as it is assumed it will be encountered again.

@abrown
Copy link
Collaborator

abrown commented Jun 9, 2023

Maybe this issue should be moved to the wasi-libc or Wasmtime repository, whichever we think is more likely the problem? cc: @sunfishcode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants