Skip to content

Unexpected behavior when calling open #246

Description

@jlb6740

#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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions