Re: Signals, sockets and threads

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Christian Thalinger writes:
 > On Thu, 2006-10-19 at 09:26 -0600, Tom Tromey wrote:
 > > Here's the code.  Looks like we originally wanted SIGUSR2 everywhere
 > > but were working around a LinuxThreads bug.
 > > 
 > > // The signal to use when interrupting a thread.
 > > #if defined(LINUX_THREADS) || defined(FREEBSD_THREADS)
 > >   // LinuxThreads (prior to glibc 2.1) usurps both SIGUSR1 and SIGUSR2.
 > >   // GC on FreeBSD uses both SIGUSR1 and SIGUSR2.
 > > #  define INTR SIGHUP
 > > #else /* LINUX_THREADS */
 > > #  define INTR SIGUSR2
 > > #endif /* LINUX_THREADS */
 > 
 > Right.  Robert told me that too, but why not using SIGHUP now
 > everywhere?

I suppose we could, but what would it fix?

Andrew.


[Index of Archives]     [Linux Kernel]     [Linux Cryptography]     [Fedora]     [Fedora Directory]     [Red Hat Development]

  Powered by Linux