Skip to content
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

Require enclave upon rmw_init() call. #247

Merged
merged 1 commit into from
Jul 7, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion rmw/include/rmw/init.h
Original file line number Diff line number Diff line change
Expand Up @@ -60,12 +60,15 @@ rmw_get_zero_initialized_context(void);
* guard conditions, and is also required to properly call `rmw_shutdown()`.
*
* \pre The given options must have been initialized
* i.e. `rmw_init_options_init()` called on it.
* i.e. `rmw_init_options_init()` called on it and
* an enclave set.
* \pre The given context must be zero initialized.
*
* \post If initialization fails, context will remain zero initialized.
*
* \remarks If options are zero-initialized, then `RMW_RET_INVALID_ARGUMENT` is returned.
* If options are initialized but no enclave is provided, then `RMW_RET_INVALID_ARGUMENT`
* is returned.
* If context has been already initialized (`rmw_init()` was called on it), then
* `RMW_RET_INVALID_ARGUMENT` is returned.
*
Expand Down