Stream: git-wasmtime

Topic: wasmtime / issue #6520 fuzzgen: Fix timeout in interprete...


view this post on Zulip Wasmtime GitHub notifications bot (Jun 05 2023 at 14:44):

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

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "fuzzing"

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 (Jun 06 2023 at 17:28):

afonso360 commented on issue #6520:

How do the timeouts work? Does the interpreter count instructions executed, and the native execution doesn't, and that's why you don't expect timeouts from native execution? Assuming that's true, this seems great.

Yes, exactly. Actually the native execution only ever returns RunResult::Success, there's nothing else it can do. Timeout is there mostly to prevent infinite loops.

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

afonso360 edited a comment on issue #6520:

How do the timeouts work? Does the interpreter count instructions executed, and the native execution doesn't, and that's why you don't expect timeouts from native execution? Assuming that's true, this seems great.

Yes, exactly. Actually the native execution only ever returns RunResult::Success, there's nothing else it can do (it can also segfault). Timeout is there mostly to prevent infinite loops.


Last updated: Nov 22 2024 at 17:03 UTC