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>
418: create wasmer dir on install for windows r=MarkMcCaskey a=xmclark
This PR creates the .wasmer dir in the home directory on windows with the inno setup installer.
Additionally, the new global wapm packages path is updated to use the correct path in the wasmer dir.
Also checking in the cargo.lock cause it hadn't been updated for 0.4.0.
Co-authored-by: Mackenzie Clark <mackenzie.a.z.c@gmail.com>
417: use $INSTALL_DIRECTORY instead of $HOME/.wasmer in install.sh r=MarkMcCaskey a=MarkMcCaskey
resolves#393
Co-authored-by: Mark McCaskey <mark@wasmer.io>
