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

✨ Return/store/log the VM ExitMessage somewhere #454

Open
2 tasks
Thomasvdam opened this issue Dec 29, 2024 · 0 comments
Open
2 tasks

✨ Return/store/log the VM ExitMessage somewhere #454

Thomasvdam opened this issue Dec 29, 2024 · 0 comments
Labels
type: feature ✨ New feature or request

Comments

@Thomasvdam
Copy link
Member

✨ Feature

When the WasmVM exits with a non-zero exit code that's from Wasmer (or the library I imagine) the result only has details in the ExitInfo.ExitMessage attribute. An example: "Error: Failed to create WASMER instance: Error while importing \"wasi_snapshot_preview1\".\"random_get\": unknown import. Expected Function(FunctionType { params: [I32, I32], results: [I32] })". Right now this data is not written to the result or stored/logged anywhere else. It would be helpful for these messages to be written to the result, stderr, or something else where it's easy to access for the developer.

Motivation

Make errors more transparent and easier to debug.

Implementation

  • Decide where this information should be written. Result seems a likely candidate since a VM error means there is no userland result, but stderr might also make sense since it's on the tally side.
  • Implement decision.
@Thomasvdam Thomasvdam added the type: feature ✨ New feature or request label Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature ✨ New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant