Description of Problem: I have two installations of Redhat Linux 7.0 (from the same CD). On one installation of Redhat7.0 my application executes perfectly fine. However, on other installation of Redhat7.0 the same application binary always gets the SIGHUP after the write() call. The application is trying to write() over the network. I ran the application through the debugger and found no errno is set and the write() call returns successful, still after the write() I get the SIGHUP. How Reproducible: I am not sure what is causing this (SIGHUP) problem to appear on only one installation of Redhat7.0 and not on other. Steps to Reproduce: 1. 2. 3. Actual Results: Expected Results: Additional Information:
(The bug had the wrong component, which is why it has not been noticed.) Why should anything like this have anything to do with glibc? This is either a kernel problem (very unlikely) or a program problem. Run strace if necessary to see what is happening. I close this bug since it has nothing to do with glibc.