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.
wait_for_pid in shell_utils_launcher must handle WIFSTOPPED condition
- Assignee:
-
Backlog - Server Tooling and Methods (STM) (Inactive)
- Reporter:
-
Andrew Morrow (Inactive)
- Votes:
-
0 Vote for this issue - Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: