Skip to content

Add exception handler to edger8r. - #222

Open
kongoshuu wants to merge 1 commit into
intel:mainfrom
kongoshuu:exception_handler
Open

Add exception handler to edger8r.#222
kongoshuu wants to merge 1 commit into
intel:mainfrom
kongoshuu:exception_handler

Conversation

@kongoshuu

Copy link
Copy Markdown

Add a exception_handler to the edger8r. If any function in .edl file is marked
as "exception_handler", it should be set the "is_exception" field in the ecall
table. This is used for users to set their own exception, like signal
handler.

Add a exception_handler to the edger8r. If any function in .edl file is marked
as "exception_handler", it should be set the "is_exception" field in the ecall
table. This is used for users to set their own exception, like signal
handler.

Signed-off-by: Chong Cai<chongc@google.com>
@ghost

ghost commented Mar 9, 2018

Copy link
Copy Markdown

What is the motivation to high light the exception function in the edl file?

@kongoshuu

Copy link
Copy Markdown
Author

This is used when a user what to register their own exception handler. They can design their own exception handling that enters an enclave by highlighting the ecall as "exception_handler". Another PR has the changed code that deals with this flag (#223 ).

@ghost

ghost commented Mar 15, 2018

Copy link
Copy Markdown

The alternative solution is, when the application get the SIGCHLD, SIGUSR1, SIGRTMIN + n, etc, the application can use another free thread to handle this exception.

@bot-cc1s-branch-sync

Copy link
Copy Markdown
Contributor

Important

🔀 The Intel® SGX SDK codebase has moved

Thank you for your contribution!
The code this pull request modifies now resides in a new repository,1 so, unfortunately, it can no longer be merged here as-is. If your change is still relevant, please re-open it against the SDK repository, where this code is now maintained.

If you have any questions or need assistance migrating, please ask here. As we complete the migration, older pull requests may eventually be closed. No work is lost, though, and you are welcome to re-open your change in the new repository at any time.

Footnotes

  1. The affected sources were migrated from confidential-computing.sgx to the dedicated confidential-computing.sgx.sdk repo. The migration covered the SDK sources (sdk/), shared headers (common/), samples (SampleCode/), and the runtime libraries (psw/urts, psw/enclave_common).

@bot-cc1s-branch-sync bot-cc1s-branch-sync added the repo-migration PR whose files moved to the SGX SDK repo (needs re-targeting) label Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

repo-migration PR whose files moved to the SGX SDK repo (needs re-targeting)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants