mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2024-11-26 15:32:05 +00:00
d6e8d224ce
This is a test code to examine native stack overflow detection logic.
The current output on my environment (macOS amd64):
```shell
====== Interpreter
stack size | fail? | leak? | exception
---------------------------------------------------------------------------
0 - 14704 | failed | leaked | Exception: native stack overflow
14704 - 17904 | failed | ok | Exception: native stack overflow
17904 - 24576 | ok | ok |
====== AOT
stack size | fail? | leak? | exception
---------------------------------------------------------------------------
0 - 18176 | failed | leaked | Exception: native stack overflow
18176 - 24576 | ok | ok |
====== AOT WAMR_DISABLE_HW_BOUND_CHECK=1
stack size | fail? | leak? | exception
---------------------------------------------------------------------------
0 - 1968 | failed | ok | Exception: native stack overflow
1968 - 24576 | ok | ok |
```
This is a preparation to work on relevant issues, including:
https://github.com/bytecodealliance/wasm-micro-runtime/issues/3325
https://github.com/bytecodealliance/wasm-micro-runtime/issues/3320
https://github.com/bytecodealliance/wasm-micro-runtime/issues/3314
https://github.com/bytecodealliance/wasm-micro-runtime/issues/3297
|
||
|---|---|---|
| .. | ||
| basic | ||
| bh-atomic | ||
| debug-tools | ||
| file | ||
| gui | ||
| inst-context | ||
| inst-context-threads | ||
| linux-perf | ||
| littlevgl/vgl-wasm-runtime/src/platform/zephyr | ||
| mem-allocator | ||
| multi-module | ||
| multi-thread | ||
| native-lib | ||
| native-stack-overflow | ||
| ref-types | ||
| sgx-ra | ||
| shared-module | ||
| socket-api | ||
| spawn-thread | ||
| terminate | ||
| wasi-threads | ||
| wasm-c-api | ||
| wasm-c-api-imports | ||
| workload | ||
| README.md | ||
Samples
- basic: Demonstrating how to use runtime exposed API's to call WASM functions, how to register native functions and call them, and how to call WASM function from native function.
- file: Demonstrating the supported file interaction API of WASI. This sample can also demonstrate the SGX IPFS (Intel Protected File System), enabling an enclave to seal and unseal data at rest.
- multi-thread: Demonstrating how to run wasm application which creates multiple threads to execute wasm functions concurrently, and uses mutex/cond by calling pthread related API's.
- spawn-thread: Demonstrating how to execute wasm functions of the same wasm application concurrently, in threads created by host embedder or runtime, but not the wasm application itself.
- wasi-threads: Demonstrating how to run wasm application which creates multiple threads to execute wasm functions concurrently based on lib wasi-threads.
- multi-module: Demonstrating the multiple modules as dependencies feature which implements the load-time dynamic linking.
- ref-types: Demonstrating how to call wasm functions with argument of externref type introduced by reference types proposal.
- wasm-c-api: Demonstrating how to run some samples from wasm-c-api proposal and showing the supported API's.
- socket-api: Demonstrating how to run wasm tcp server and tcp client applications, and how they communicate with each other.
- native-lib: Demonstrating how to write required interfaces in native library, build it into a shared library and register the shared library to iwasm.
- sgx-ra: Demonstrating how to execute Remote Attestation on SGX with librats, which enables mutual attestation with other runtimes or other entities that support librats to ensure that each is running within the TEE.
- workload: Demonstrating how to build and run some complex workloads, e.g. tensorflow-lite, XNNPACK, wasm-av1, meshoptimizer and bwa.
- debug-tools: Demonstrating how to symbolicate a stack trace.