Program terminated with signal SIGKILL, Killed.

Open
#4,392 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
wasm
Domain
compilers

Research direction

Start by running ./bin/wasm-ctor-eval POC5 using the supplied POC5.zip and version_103 context. Inspect the wasm-ctor-eval entry point and capture why the process receives SIGKILL. Done means the reproducer no longer terminates this way, or the issue has a documented, reproducible diagnosis and appropriate test coverage.

Written by the indexing model from the issue text.

Description

Version:

version_103

System information

command:

./bin/wasm-ctor-eval POC5

POC5.zip

Result

Program terminated with signal SIGKILL, Killed.

Dominant language
WebAssembly
Stars
8.6k
Forks
885
Avg merge
2d 1h
Merged PRs (30d)
70

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/binaryen

All issues in WebAssembly/binaryen

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.