InterruptChildWithSigHup of ninja_test fails and other cases pass, how to troubleshoot the problem?
liangbosheng opened this issue · comments
for ninja 1.11.0
1、run InterruptChildWithSigHup of ninja_test in some linux distro，it failed
2、as a contrast, run InterruptChildWithSigHup of ninja_test in Ubuntu 20.04，it passed
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.
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 handlefor 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.
- This phenomenon occured before using the debugger.
- thanks for these tips about "the default signal settings" and "process handle", I will check these.