[SERVER-36724] wait_for_pid in shell_utils_launcher must handle WIFSTOPPED condition Created: 17/Aug/18 Updated: 06/Dec/22 Resolved: 27/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Tooling & Methods
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 11 | ||||
| Description |
|
We handle WIFEXITED and WIFSIGNALED, but we don't seem to handle WIFSTOPPED (or, on linux WIFCONTINUED). This is problematic because in cases of timeouts, we may connect a debugger which could lead to a WIFSTOPPED case. We should handle these additional cases. |