-
Notifications
You must be signed in to change notification settings - Fork 885
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
Silence the libevent warning when a proc abnormally terminates by cleaning up the error registrations #2251
Conversation
…aning up the error registrations
peer->index, NULL); | ||
PMIX_RELEASE(peer); | ||
/* remove all registered event handlers so libevent doesn't complain */ | ||
PMIX_LIST_FOREACH_SAFE(reginfoptr, regnext, &pmix_server_globals.client_eventregs, pmix_regevents_info_t) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you need a lock around accessing the members of this list? I.e., with a name like "globals", does that imply that another thread may be accessing it at the same time?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, we are in an event and therefore safe from any other thread access
/* remove all registered event handlers so libevent doesn't complain */ | ||
PMIX_LIST_FOREACH_SAFE(reginfoptr, regnext, &pmix_server_globals.client_eventregs, pmix_regevents_info_t) { | ||
if (reginfoptr->peer == peer) { | ||
PMIX_RELEASE(reginfoptr); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per IM discussion -- @rhc54 is going to bring over another change here for removing the item from the list.
Travis looks kind of borked up again. I'll give it another 30 minutes |
No description provided.