From: Bart Van Assche Date: Sun, 27 Apr 2008 06:14:06 +0000 (+0000) Subject: The sigkill regression test no longer attempts to set signal handlers for the signal... X-Git-Tag: svn/VALGRIND_3_4_0~692 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=66a4a864e73d40a01473a0d62b7e7d3e20898255;p=thirdparty%2Fvalgrind.git The sigkill regression test no longer attempts to set signal handlers for the signal numbers 32 and 33. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7931 --- diff --git a/memcheck/tests/sigkill.c b/memcheck/tests/sigkill.c index 8a757f90b7..10b87dd69e 100644 --- a/memcheck/tests/sigkill.c +++ b/memcheck/tests/sigkill.c @@ -19,10 +19,13 @@ main (void) int i; int rc; for (i = 1; i <= 65; i++) { + // Skip signals 32 and 33, since these are used by LinuxThreads. Some + // glibc versions do not invoke the sigaction system call for these + // signals. // skip signals 63 and 64: some systems say "warning, ignored attempt // to catch 32 because it's used internally by Valgrind", others say // "invalid argument". - if (i == 63 || i == 64) { + if (i == 32 || i == 33 || i == 63 || i == 64) { continue; } // different systems sa.sa_flags = 0; diff --git a/memcheck/tests/sigkill.stderr.exp b/memcheck/tests/sigkill.stderr.exp index 2f1c7546d9..5d209b03ba 100644 --- a/memcheck/tests/sigkill.stderr.exp +++ b/memcheck/tests/sigkill.stderr.exp @@ -96,12 +96,6 @@ getting signal 30: Success setting signal 31: Success getting signal 31: Success -setting signal 32: Success -getting signal 32: Success - -setting signal 33: Success -getting signal 33: Success - setting signal 34: Success getting signal 34: Success