[SERVER-20242] launchProcess in the shell should _exit rather than quickExit after fork Created: 01/Sep/15 Updated: 19/Sep/15 Resolved: 01/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 3.1.7 |
| Fix Version/s: | 3.1.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | Build the shell with address sanitizer invoke runProgram with an invalid executable with the leak checker on. See leak information. |
| Sprint: | Platform 9 (09/18/15) |
| Participants: |
| Description |
|
launchProcess, which underlies runProgram, in the shell calls quickExit after a fork if it fails to dup fds or if the exec fails. This means that some atexit handlers will be called incorrectly. In particular, this triggers the leak checker, which we didn't intend to run as a result of runProgram. |
| Comments |
| Comment by Githook User [ 01/Sep/15 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: launchProcess in the shell should _exit after fork if the exec fails, |