| commit | 67aa76d3b7e425b58954c334b320cf90e763411b | |
| author | Phil Miller <mille121@illinois.edu> | |
| Mon, 10 Apr 2017 22:20:21 +0000 (10 17:20 -0500) | ||
| committer | Michael Robson <mprobson@illinois.edu> | |
| Thu, 13 Apr 2017 17:26:43 +0000 (13 12:26 -0500) | ||
| tree | 0c2a3d46045ec97d4794769939a07406173c5a1d | treesnapshot (tar.gz zip) |
| parent | 400488388a0f073f880b0d94bfc7de80e029db14 | commitdiff |
Bug #700: Make the user-facing CkExit() function idempotent
User code could get into trouble by having multiple dynamic calls to
CkExit(). This could arise in applications like state-space search,
where any object finding one of many solutions might call it. It could
also arise in other structures as well. When this happened, modules
that ran analysis and cleanup code at shutdown would be
short-circuited, and unpredictable results would ensue.
The CkExit() call itself was made idempotent by setting and checking a
flag indicating that the exit process was already in progress. Rather
than calling the same user-facing CkExit() again, modules with
exit-time operations now use a separate function, CkContinueExit(), to
advance the exit process.
Change-Id: I61652ae52b2059ea302c085c1391b4cecf9dd019
User code could get into trouble by having multiple dynamic calls to
CkExit(). This could arise in applications like state-space search,
where any object finding one of many solutions might call it. It could
also arise in other structures as well. When this happened, modules
that ran analysis and cleanup code at shutdown would be
short-circuited, and unpredictable results would ensue.
The CkExit() call itself was made idempotent by setting and checking a
flag indicating that the exit process was already in progress. Rather
than calling the same user-facing CkExit() again, modules with
exit-time operations now use a separate function, CkContinueExit(), to
advance the exit process.
Change-Id: I61652ae52b2059ea302c085c1391b4cecf9dd019