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
mc-sgx-panic-log
mc-sgx-io
mc-sgx-io-untrusted
mc-sgx-sync
mc-sgx-panic
The text was updated successfully, but these errors were encountered:
nick-mobilecoin
No branches or pull requests
mc-sgx-io
tomc-sgx-io-untrusted
#21mc-sgx-io
#22Should we derive ocall function signature from edl output?Captured in Consider ergonomics around dependent OCALLs #52mc-sgx-panic-log
#24Use a static buffer for the panic stderr instead of allocating a StringThis will be handled in Thread (mc-sgx-sync
) #29 done in Use a static buffer for panic messages #41mc-sgx-panic
#48Re-evaluate the loop{} used for logging panic handler. Discussion from Use a static buffer for panic messages #41 (comment)
The loop will keep the thread going indefinitely, but not actually stop it. The current implementation was modeled after, https://doc.rust-lang.org/nomicon/panic-handler.html, which doesn't seem to halt the thread, but more or less spins it off into oblivion.
The text was updated successfully, but these errors were encountered: