Sergei, can you report it as a separate bug? Can we fix it with AutoInactiveDestroy?
You can also initialize 'end' to 1, but then reset it to 0 just before the 'while' loop. I'm not sure if that will remove the race between signal handler setup code in the child process and the SIGHUP sending in the parent completely, but should certainly reduce its probability.
Sergei, can you report it as a separate bug? Can we fix it with AutoInactiveDes troy?
You can also initialize 'end' to 1, but then reset it to 0 just before the 'while' loop. I'm not sure if that will remove the race between signal handler setup code in the child process and the SIGHUP sending in the parent completely, but should certainly reduce its probability.