|
From: Jeremy F. <je...@go...> - 2003-11-14 16:45:35
|
On Fri, 2003-11-14 at 06:22, Dimitri Papadopoulos-Orfanos wrote: > Hi, > > I get these warnings on a Red Hat 9 machine: > > $ valgrind ls > [...] > ==14433== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. > ==14433== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. > ==14433== Using valgrind-2.0.0, a program supervision framework for > x86-linux. > ==14433== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. > ==14433== Estimated CPU clock rate is 1995 MHz > ==14433== For more details, rerun with: -v > ==14433== > ==14433== Warning: attempt to set SIGKILL handler in __NR_sigaction. > ==14433== Warning: attempt to set SIGSTOP handler in __NR_sigaction. > [...] > > What do they mean exactly? > Should these warnings be ignored? > Should the program be fixed? They're almost not worth warning about. SIGKILL and SIGSTOP cannot be caught or handled in any way, so trying to set them to anything other than SIG_DFL with sigaction is an error - but a very minor one with no side-effects. This warning is common with code which does something like: for(sig = 1; sig < NSIG; sig++) sigaction(sig, &sa, NULL); So ignore it unless you're being pedantic. J |