We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sock_shutdown
fd_close any file descriptor then attempting to call sock_shutdown on it causes wasmedge CLI to segfault.
fd_close
No response
(module (type (func)) (type (func (param i32 i32 i32) (result i32))) (type (func (param i32))) (type (func (param i32) (result i32))) (import "wasi_snapshot_preview1" "sock_accept" (func $sock_shutdown (type 1))) (import "wasi_snapshot_preview1" "proc_exit" (func $proc_exit (type 2))) (import "wasi_snapshot_preview1" "fd_close" (func $fd_close (type 3))) (func $_start (call $fd_close (i32.const 2) ) drop (call $sock_shutdown (i32.const 2) (i32.const 27) (i32.const 1337) ) call $proc_exit ) (memory 2) (export "memory" (memory 0)) (export "_start" (func $_start)) )
wat2wasm shutdown.wat -o shutdown.wasm
wasmedge shutdown.wasm
$ wasmedge shutdown.wasm Segmentation fault (core dumped)
CLI
0.13.5
Fedora 39
amd64
The text was updated successfully, but these errors were encountered:
Reproducible
Sorry, something went wrong.
[WASI] Check fd valid on socket_accept, fix #3041
socket_accept
17d8e9b
Signed-off-by: Shen-Ta Hsieh <beststeve@secondstate.io>
60773e5
No branches or pull requests
Summary
fd_close
any file descriptor then attempting to callsock_shutdown
on it causes wasmedge CLI to segfault.Current State
No response
Expected State
No response
Reproduction steps
wat2wasm shutdown.wat -o shutdown.wasm
wasmedge shutdown.wasm
Screenshots
Any logs you want to share for showing the specific issue
No response
Components
CLI
WasmEdge Version or Commit you used
0.13.5
Operating system information
Fedora 39
Hardware Architecture
amd64
Compiler flags and options
No response
The text was updated successfully, but these errors were encountered: