-
Notifications
You must be signed in to change notification settings - Fork 931
ess/singleton: do not put component strings into the environment #518
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
Conversation
|
@rhc Was seeing SEGV in getenv due to ess/singleton. This commit fixes it. Probably applies to 1.8 as well. |
|
@hjelmn I think we've been standardizing on opal_setenv instead of using setenv itself. |
|
Ok, I will update the commit. |
|
@rhc54 Fixed. Also changed the unsetenv calls to use opal_unsetenv. |
putenv requires that any string put into the environment is not changed or freed. That is not the case with constant strings as they will go away when dlclose is called on the component. Instead, just use opal_setenv which does not have this restriction. Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>
|
|
Ok. Merging and will open a PR for 1.8.5 |
ess/singleton: do not put component strings into the environment
|
Refer to this link for build results (access rights to CI server needed): |
|
|
Refer to this link for build results (access rights to CI server needed): |
v2.x standardize verbosity
putenv requires that any string put into the environment is not
changed or freed. That is not the case with constant strings as they
will go away when dlclose is called on the component. Instead, just
use setenv which does not have this restriction.
Signed-off-by: Nathan Hjelm hjelmn@lanl.gov