Fix build for SGX_DEBUG=1 #419
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use cargo --release also in case of SGX_DEBUG=1 and hence also the corresponding target/release folder. Closes #375
murerfel
force-pushed
the
bugfix/fm-sgx-debug-mode-375
branch
from
fef9d9b
to
958e307
Compare
|
It might not be optimal, but until now, we never made use of the debugger anyhow. However, for your information, the enclave can be debugged if |
Ah good to know! 🚀 It would certainly be nice in the future to have debug capabilities |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use
cargo --releasealso in case ofSGX_DEBUG=1and hence also the correspondingtarget/releasefolder.This still might not be the best debugging experience - but that would be a lot tougher to achieve (if not impossible), considering the nature of the enclave (which cannot be debugged by design).
Closes #375