fweimer added a new comment to an issue you are following:
``
@walters, I think you should be able to reproduce this issue if you trigger PID reuse.
After the `clone` call, glibc's cached view of the PID does not match the kernel PID.
The assertion triggers if the original (pre-`clone`) PID is reused for the new child
process.
The assertion is correct in the sense that glibc does not work properly if the PID cache
is out of sync. In rawhide, this is fixed with the removal of the PID cache.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6602