You can use sigprocmask() to block out sigpipe. The thread that fails to write() to the socket with error EPIPE is the one. On 28 Aug 2002, devraj sanyal wrote: > i have a multi-threaded application. these applications > uses sockets. so i have to check for sigpipe. > my problem is to identify which thread is responsible for > the signal. --