The new-style atexit implementation used /also/ propagates across fork calls, so every child which is forked ends up calling finish(). This is marginally annoying except for Subversion modules, where the 'module_has_conflict' check run by log_command() technically involves a forked child for the implementation. Since the abnormal-end finish that gets run by atexit takes priority over the result code from module_has_conflict it appears that there's always a conflict. Instead, just make sure that finish() is only called for real from the process that installed the handler in the first place.wilder
parent
2462ff493f
commit
7c2233c94c
1 changed files with 2 additions and 1 deletions
Loading…
Reference in new issue