Skip to content

wamr (AOT mode) crashes and throws unhandled SIGSEGV, Aborted #4622

@Theaamadu

Description

@Theaamadu

Subject of the issue

I have generated a wasm file as a test case and ran it with wasmtime, wasmedge, wamr (AOT & JIT mode), and wasmer runtimes. The wamr (AOT & JIT mode) crashes and throws unhandled SIGSEGV, Aborted whereas the other runtimes successfully execute the wasm file.

Test case

wamr-aot-aborted.zip

Your environment

  • Host OS (Ubuntu 22.04)
  • WAMR version (iwasm 2.4.1 and wamrc 2.2.0), platform (Linux), cpu architecture (x86_64), running mode (AOT and JIT), etc.

Steps to reproduce

  1. Extract the zip file
  2. Run wamrc --xip --enable-builtin-intrinsics=all --enable-multi-thread --bounds-checks=1 -o $OUTPUT-FILE $WASM-FILE
  3. Run iwasm --heap-size=0 -f foo $OUTPUT-FILE
  4. Run (JIT mode) iwasm --heap-size=0 --llvm-jit -f foo $WASM-FILE
  5. See error

Expected behavior

The output of wamr (AOT & JIT mode) should be start which indicates that the testcase has been executed successfully.

Actual behavior

wamr (AOT & JIT mode) crashes and throws unhandled SIGSEGV, Aborted out.

Extra Info

Can you please confirm if this is a bug? Thanks in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions