Skip to content

Conversation

wenyongh
Copy link
Contributor

@wenyongh wenyongh commented Aug 7, 2024

Some host environment may also create an signal alternate stack and access
it after the wasm runtime exits, the runtime should backup the stack info and
restore it before thread exits.

The issue was found in golang:

signal 23 received on thread with on signal stack
fatal error: non-Go code disabled signaltstack

@TianlongLiang
Copy link
Collaborator

LGTM

@wenyongh wenyongh merged commit da31c07 into bytecodealliance:main Aug 12, 2024
385 checks passed
@wenyongh wenyongh deleted the fix_sigaltstack branch August 14, 2024 01:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants