We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ostest build with CONFIG_SIG_DEFAULT and task grouping will crash during mqueue_test
Run Using the x86_64 ostest build with CONFIG_SIG_DEFAULT=y on qemu or Jailhouse.
At the end of mqueue_test, pthread_kill SIGKILL is used to delete the reciver thread.
With CONFIG_SIG_DEFAULT, it will trigger abnormal_termination.
Furthermore, because of task grouping, this will not only terminate the thread but also other threads in the whole group, including the ostest thread.
This in terms cause the DEBUGASSERT in waitpid to failed because the threads are terminated unexpectedly and child no longer exit in groups.
The test will crash as #955.
I think this is the root cause of #955.
I am not definite whether this is simply a bad DEBUGASSERT or mqueue_test should fundamentally stop using pthread_kill.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem
ostest build with CONFIG_SIG_DEFAULT and task grouping will crash during mqueue_test
How to Reduplicate the problem
Run Using the x86_64 ostest build with CONFIG_SIG_DEFAULT=y on qemu or Jailhouse.
Reason of Problem
At the end of mqueue_test, pthread_kill SIGKILL is used to delete the reciver thread.
With CONFIG_SIG_DEFAULT, it will trigger abnormal_termination.
Furthermore, because of task grouping, this will not only terminate the thread but also other threads in the whole group, including the ostest thread.
This in terms cause the DEBUGASSERT in waitpid to failed because the threads are terminated unexpectedly and child no longer exit in groups.
The test will crash as #955.
How should it behave
Related Issue
I think this is the root cause of #955.
Other thoughts
I am not definite whether this is simply a bad DEBUGASSERT or mqueue_test should fundamentally stop using pthread_kill.
The text was updated successfully, but these errors were encountered: