issue on waitpid

Open
#496 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, linux
Domain
operating-systems

Research direction

Start by reproducing the Linux process v2 scenario described: a child is killed while async_wait is active and io_context runs on four threads. Trace the terminate and async_wait paths around waitpid and verify the completion does not produce an unexpected ECHILD error when both paths observe the child.

Written by the indexing model from the issue text.

Description

boost version 1.88

I use process v2 on linux
My io_context is run by 4 threads

I have a child process running and I have started an async_wait.
I kill child process, then inside terminate, waitpid is called
On async_wait completion, waitpid is also called and waitpid returns ECHILD what go to this error: "No child processes"

Dominant language
C++
Stars
145
Forks
151
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/process

All issues in boostorg/process

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.