Stream: git-wasmtime

Topic: wasmtime / issue #6262 wasmtime: Overhaul trampolines

view this post on Zulip Wasmtime GitHub notifications bot (Apr 21 2023 at 18:44):

github-actions[bot] commented on issue #6262:

Subscribe to Label Action

cc @peterhuene

<details>
This issue or pull request has been labeled: "wasmtime:c-api"

Thus the following users have been cc'd because of the following labels:

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

view this post on Zulip Wasmtime GitHub notifications bot (Apr 21 2023 at 19:02):

fitzgen commented on issue #6262:

Run cargo vet --locked
Vetting Failed!

1 unvetted dependencies:
  bumpalo:3.12.0 missing ["safe-to-deploy"]

Unclear why this is failing, since I have a wildcard audit for bumpalo.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 21 2023 at 19:04):

fitzgen commented on issue #6262:

I guess I needed to run cargo vet without --locked locally and commit the changes.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 21 2023 at 20:55):

fitzgen commented on issue #6262:

Everything is passing except s390x -- I wonder if some little endian assumptions snuck in somewhere.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 28 2023 at 16:50):

kpreisser commented on issue #6262:

Hi! It seems this change has introduced a regression in the Wasmtime C API, which causes a panic similar to the following to occur e.g. in the wasmtime-dotnet unit tests:

thread '<unnamed>' panicked at '0x0 > 0xdeb7f7d2f0', crates\runtime\src\traphandlers\backtrace.rs:301:13

Please see https://github.com/bytecodealliance/wasmtime-dotnet/pull/245#issuecomment-1527820325 for more details and for a reproduction case using wasmtime-dotnet (C#, .NET 7.0).
Thanks!

view this post on Zulip Wasmtime GitHub notifications bot (Apr 28 2023 at 17:00):

kpreisser edited a comment on issue #6262:

Hi! It seems this change has introduced a regression in the Wasmtime C API, which causes a panic similar to the followings to occur e.g. in the wasmtime-dotnet unit tests:

thread '<unnamed>' panicked at '0x0 > 0xdeb7f7d2f0', crates\runtime\src\traphandlers\backtrace.rs:301:13

thread '<unnamed>' panicked at '0x2 > 0x7f0c413be330', crates/runtime/src/traphandlers/backtrace.rs:301:13

Please see https://github.com/bytecodealliance/wasmtime-dotnet/pull/245#issuecomment-1527820325 for more details and for a reproduction case using wasmtime-dotnet (C#, .NET 7.0).
Thanks!

view this post on Zulip Wasmtime GitHub notifications bot (Apr 28 2023 at 17:38):

kpreisser edited a comment on issue #6262:

Hi! It seems this change has introduced a regression in the Wasmtime C API, which causes a panic similar to the following ones to occur e.g. in the wasmtime-dotnet unit tests:

thread '<unnamed>' panicked at '0x0 > 0xdeb7f7d2f0', crates\runtime\src\traphandlers\backtrace.rs:301:13

thread '<unnamed>' panicked at '0x2 > 0x7f0c413be330', crates/runtime/src/traphandlers/backtrace.rs:301:13

Please see https://github.com/bytecodealliance/wasmtime-dotnet/pull/245#issuecomment-1527820325 for more details and for a reproduction case using wasmtime-dotnet (C#, .NET 7.0).
Thanks!

Last updated: Dec 23 2024 at 13:07 UTC