-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
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
Command doesn't exit if thread is stuck in blocking I/O #109
Labels
Comments
I expect this to be fixed alongside #18. |
mzohreva
added a commit
to mzohreva/rust
that referenced
this issue
Apr 23, 2020
Related issues: - fortanix/rust-sgx#109
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this issue
Apr 28, 2020
Process termination test for SGX The issue is described in fortanix/rust-sgx#109 cc @jethrogb
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this issue
Apr 28, 2020
Process termination test for SGX The issue is described in fortanix/rust-sgx#109 cc @jethrogb
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this issue
May 1, 2020
Process termination test for SGX The issue is described in fortanix/rust-sgx#109 cc @jethrogb
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
May 13, 2020
Process termination test for SGX The issue is described in fortanix/rust-sgx#109 cc @jethrogb
Yeah, this was fixed in #223 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This program may not terminate:
This is because when the main thread exits, the second thread is likely to be blocking in an
accept()
call. Therefore, that thread never terminates and the main thread (out of the enclave) is waiting indefinitely for that second thread to finish.The text was updated successfully, but these errors were encountered: