fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-13 06:15:33 +00:00
Code Issues Projects Releases Wiki Activity
704c783b54
wasmer/lib
History
bors[bot] 704c783b54 Merge #414 
414: Exception logging (win32): Handle error codes correctly, add some more strings r=syrusakbary a=hrydgard

Ran into a situation with an unknown exception from Cranelift (will probably report that one separately). Turns out the signum was "1" though which does not seem to correspond to any of the Windows error codes, except possibly STATUS_GUARD_PAGE which is 0x80000001, but only if we lost the top bit somewhere.

On Windows, exceptions seemed to be trapped by callProtected, which is implemented here: cade9a666f/lib/win-exception-handler/exception_handling/exception_handling.c . It did not seem to correctly store and retrieve the exception code, instead always returning 1: ```longjmp(jmpBuf, 1);```

So I fixed it. And now the log output looks like this:

```
unhandled trap at 1560d5e7bab - code #c0000005: segmentation violation
```


Co-authored-by: Henrik Rydgård <henrik.rydgard@embark-studios.com>
Co-authored-by: Syrus Akbary <me@syrusakbary.com>
Co-authored-by: Mackenzie Clark <mackenzie.a.z.c@gmail.com>
2019-05-06 19:54:21 +00:00
..
clif-backend Exception logging (win32): Handle error codes correctly, add some more strings. 2019-05-02 12:45:52 +02:00
emscripten Fixed ioctl in Unix. Fixed provied main arguments 2019-05-05 13:55:40 -07:00
llvm-backend Merge branch 'master' into update-version-numbers-to-4 2019-05-01 09:27:38 -07:00
middleware-common Update lib/middleware-common/Cargo.toml 2019-05-01 11:32:57 -07:00
runtime update version to 0.4.0 2019-04-29 13:26:51 -07:00
runtime-abi Merge branch 'master' into update-version-numbers-to-4 2019-05-01 09:27:38 -07:00
runtime-c-api update version to 0.4.0 2019-04-29 13:26:51 -07:00
runtime-core codegen: Remove unused LoadError import 2019-05-06 20:42:35 +03:00
singlepass-backend Exception logging (win32): Handle error codes correctly, add some more strings. 2019-05-02 12:45:52 +02:00
spectests update version to 0.4.0 2019-04-29 13:26:51 -07:00
wasi update version to 0.4.0 2019-04-29 13:26:51 -07:00
win-exception-handler Exception logging (win32): Handle error codes correctly, add some more strings. 2019-05-02 12:45:52 +02:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Renamed dynasm backend to singlepass 2019-04-11 12:44:03 -07:00

README.md

Wasmer Libraries

Wasmer is modularized into different libraries, separated into three main sections:

Runtime

The core of Wasmer is the runtime, which provides the necessary abstractions to create a good user experience when embedding.

The runtime is divided into two main libraries:

  • runtime-core: The main implementation of the runtime.
  • runtime: Easy-to-use API on top of runtime-core.

Integrations

The integration builds on the Wasmer runtime and allow us to run WebAssembly files compiled for different environments.

Wasmer intends to support different integrations:

  • WASI: run WebAssembly files with the WASI ABI.
  • Emscripten: run Emscripten-generated WebAssembly files, such as Lua or nginx.
  • Go ABI: we will work on this soon! Want to give us a hand? ✋
  • Blazor: research period, see tracking issue

Backends

The Wasmer runtime is designed to support multiple compiler backends, allowing the user to tune the codegen properties (compile speed, performance, etc) to best fit their use case.

Currently, we support multiple backends for compiling WebAssembly to machine code:

  • singlepass-backend: Single pass backend - super fast compilation, slower runtime speed
  • clif-backend: Cranelift backend - slower compilation, normal runtime speed
  • llvm-backend: LLVM backend - slow compilation, native runtime speed