Skip to content

Keep tracing other processes when a child is killed by a signal - #6

Open
Bortlesboat wants to merge 1 commit into
thundergolfer:mainfrom
Bortlesboat:follow-forks-signaled-child
Open

Bortlesboat wants to merge 1 commit into
thundergolfer:mainfrom
Bortlesboat:follow-forks-signaled-child

Conversation

@Bortlesboat

Copy link
Copy Markdown

With -f, the WaitStatus::Signaled arm always broke out of the trace loop, so the first traced child killed by a signal ended the trace and the parent's later syscalls were never shown. It now stops only once no traced PIDs remain, like the Exited arm. Added test_follow_forks_continues_after_child_killed_by_signal; cargo test -- --test-threads=1 passes on Linux.

The Signaled arm always broke out of the trace loop, so with -f the
first traced child to die from a signal ended the whole trace and left
the remaining tracees behind. Only stop once no traced PIDs are left,
as the Exited arm already does.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant