From: Dmitry V. L. <ld...@al...> - 2012-01-18 19:47:00
|
On Wed, Jan 18, 2012 at 03:56:38PM +0100, Denys Vlasenko wrote: [...] > So, why we even have TCB_SIGTRAPPED? No one knows. It predates > version control: this code was present in the initial commit, > in 1999. > > Moreover, TCB_SIGTRAPPED is not used in sys_rt_sigaction, > only in obsolete sys_signal, sys_sigaction, sys_sigsetmask, > and in some dead non-Linux code. > > I think whatever bug it was fixing is gone long ago - > at least as long as sys_rt_sigaction is used by glibc. > Again, since glibc (and uclibc) uses sys_rt_sigaction > and sys_sigprocmask, modified code paths are not used > by most programs anyway. Looks reasonable. Let's see whether this TCB_SIGTRAPPED thing will strike us back or not. -- ldv |