Red Hat Bugzilla – Bug 171332
NPTL sighup bug
Last modified: 2012-06-20 12:57:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5
Description of problem:
From the URL:
one friend noticed that multithreaded programs (VMware...) behave erraticaly
when started from rxvt or xterm with -e option. We've traced it down to some
strange SIGHUP delivery.
When process is session leader, is it supposed to receive SIGHUP when child
thread terminates? It did not receive SIGHUP under non-NPTL library, and
IMHO it was correct behavior. Now all exiting threads cause SIGHUP to be
delivered to the parent, and parent (I'd say correctly) assumes that
connection to the program was broken and terminates.
This is fairly serious. And while we can kludge around it by ignoring sighup in c, java has the same problem, and I don't think we can work around it there.
Previously mentioned URL includes sample code, and later in that email thread there's a patch.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run test code
This appears to have been fixed in kernel 2.6.11
I'm sorta curious what's going on with this. This seems like a fairly major bug
to me, as it comes up execing any multithreaded app. Any plans?
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.