Skip to content
New issue

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

InterruptChildWithSigHup of ninja_test fails and other cases pass, how to troubleshoot the problem? #2441

Open
liangbosheng opened this issue May 6, 2024 · 2 comments

Comments

@liangbosheng
Copy link

liangbosheng commented May 6, 2024

for ninja 1.11.0

1、run InterruptChildWithSigHup of ninja_test in some linux distro,it failed

linux_dist

2、as a contrast, run InterruptChildWithSigHup of ninja_test in Ubuntu 20.04,it passed

ubuntu

@digit-google
Copy link
Contributor

Does that only occur under the debugger? In this case have you checked the default signal settings on each platform?
In other words, what is the output of process handle for the SIGHUP signal in each debugging session? If they are different, that would explain what you are seeing.

Apart from that, we will need more information about what you mean by "some linux distro" to be able to reproduce this.

@liangbosheng
Copy link
Author

Does that only occur under the debugger? In this case have you checked the default signal settings on each platform? In other words, what is the output of process handle for the SIGHUP signal in each debugging session? If they are different, that would explain what you are seeing.

Apart from that, we will need more information about what you mean by "some linux distro" to be able to reproduce this.

  1. This phenomenon occured before using the debugger.
  2. thanks for these tips about "the default signal settings" and "process handle", I will check these.

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

No branches or pull requests

2 participants