Stream: git-wasmtime

Topic: wasmtime / issue #7633 A difference between windows and l...

view this post on Zulip Wasmtime GitHub notifications bot (Dec 05 2023 at 12:31):

Userzxcvbvnm added the bug label to Issue #7633.

view this post on Zulip Wasmtime GitHub notifications bot (Dec 05 2023 at 12:31):

Userzxcvbvnm opened issue #7633:

Test Case

The test.c file is uploaded as
test-c.txt

The test.wasm file is uploaded as
test-wasm.txt

Steps to Reproduce

We create a normal file Data/hello.txt and write some initial content into the file.
using command wasmtime run --dir=./Data test.wasm to execute the wasm file.

Actual Results

In windows, wasmtime do not write any bytes into the file and prints:

Successfully get the file fd.
Current offset: 0
Wrote 0 bytes to the file.
File Size: 33 bytes
Leave snapshot.

In linux, wasmtime writes null characters (\u0000) into the file and prints:

Successfully get the file fd.
Current offset: 0
Wrote 0 bytes to the file.
File Size: 50 bytes
Leave snapshot.

There is a difference between executing the wasm file in windows and linux.
Maybe in linux, this could be a bug?

Versions and Environment

Ubuntu 20.04 (amd64)
Windows 10 (x86_64)
wasmtime 13.0.0

view this post on Zulip Wasmtime GitHub notifications bot (Dec 05 2023 at 12:38):

Userzxcvbvnm edited issue #7633:

Test Case

The test.c file is uploaded as
test-c.txt

The test.wasm file is uploaded as
test-wasm.txt

Steps to Reproduce

We create a normal file Data/hello.txt and write some initial content into the file.
using command wasmtime run --dir=./Data test.wasm to execute the wasm file.

Actual Results

In linux, wasmtime do not write any bytes into the file and prints:

Successfully get the file fd.
Current offset: 0
Wrote 0 bytes to the file.
File Size: 33 bytes
Leave snapshot.

In windows, wasmtime writes null characters (\u0000) into the file and prints:

Successfully get the file fd.
Current offset: 0
Wrote 0 bytes to the file.
File Size: 50 bytes
Leave snapshot.

There is a difference between executing the wasm file in windows and linux.
Maybe in linux, this could be a bug?

Versions and Environment

Ubuntu 20.04 (amd64)
Windows 10 (x86_64)
wasmtime 13.0.0

view this post on Zulip Wasmtime GitHub notifications bot (Dec 05 2023 at 12:39):

Userzxcvbvnm edited issue #7633:

Test Case

The test.c file is uploaded as
test-c.txt

The test.wasm file is uploaded as
test-wasm.txt

Steps to Reproduce

We create a normal file Data/hello.txt and write some initial content into the file.
using command wasmtime run --dir=./Data test.wasm to execute the wasm file.

Actual Results

In linux, wasmtime do not write any bytes into the file and prints:

Successfully get the file fd.
Current offset: 0
Wrote 0 bytes to the file.
File Size: 30 bytes
Leave snapshot.

In windows, wasmtime writes null characters (\u0000) into the file and prints:

Successfully get the file fd.
Current offset: 0
Wrote 0 bytes to the file.
File Size: 50 bytes
Leave snapshot.

There is a difference between executing the wasm file in windows and linux.
Maybe in linux, this could be a bug?

Versions and Environment

Ubuntu 20.04 (amd64)
Windows 10 (x86_64)
wasmtime 13.0.0

view this post on Zulip Wasmtime GitHub notifications bot (Dec 05 2023 at 17:18):

pchickey commented on issue #7633:

Thanks for the report. In the future, can you add to your reports the traces given when WASMTIME_LOG=wasmtime_wasi=trace is set in your host environment?

view this post on Zulip Wasmtime GitHub notifications bot (Feb 14 2024 at 00:58):

alexcrichton closed issue #7633:

Test Case

The test.c file is uploaded as
test-c.txt

The test.wasm file is uploaded as
test-wasm.txt

Steps to Reproduce

We create a normal file Data/hello.txt and write some initial content into the file.
using command wasmtime run --dir=./Data test.wasm to execute the wasm file.

Actual Results

In linux, wasmtime do not write any bytes into the file and prints:

Successfully get the file fd.
Current offset: 0
Wrote 0 bytes to the file.
File Size: 30 bytes
Leave snapshot.

In windows, wasmtime writes null characters (\u0000) into the file and prints:

Successfully get the file fd.
Current offset: 0
Wrote 0 bytes to the file.
File Size: 50 bytes
Leave snapshot.

There is a difference between executing the wasm file in windows and linux.
Maybe in linux, this could be a bug?

Versions and Environment

Ubuntu 20.04 (amd64)
Windows 10 (x86_64)
wasmtime 13.0.0

Last updated: Oct 23 2024 at 20:03 UTC