|
From: Avery P. <ape...@ni...> - 2003-11-17 17:56:01
|
On Mon, Nov 17, 2003 at 10:37:43AM +0000, Nicholas Nethercote wrote: > Warning: ignored attempt to set SIGKILL handler in sigaction(); > the SIGKILL signal is uncatchable > > > Also, for programs that set the sighandler in a loop - apparently > > include ls on some systems - I bet they're usually *disabling* a special > > handler, ie. 'sa' is NULL in the code fragment below. It would probably > > give fewer spurious warnings if we just didn't print a warning when > > sa==NULL. > > No. Valgrind doesn't print the warning when sa==NULL. In that case, I think the warning is valid, and there's no question about removing it - people should really only set signal handlers on signals they understand, not try to foolishly catch every single one as if they knew what to do when they got them. Have fun, Avery |