Fix nptl/tst-kill5 not to presume SIGRTMAX exists.

git-mirror · Feb 6, 2015 · ebf7d6e · ebf7d6e
1 parent ca0e067
commit ebf7d6e
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/ChangeLog b/ChangeLog
@@ -1,5 +1,7 @@
 2015-02-06  Roland McGrath  <roland@hack.frob.com>
 
+	* nptl/tst-kill5.c (do_test): Use INT_MAX rather than SIGRTMAX + 10.
+
 	* nptl/tst-join5.c: Drop #include <sys/syscall.h>.
 	(wait_code): New function replaces macro.
 	Call nanosleep rather than syscall.

diff --git a/nptl/tst-kill5.c b/nptl/tst-kill5.c
@@ -21,14 +21,15 @@
 #include <signal.h>
 #include <stdio.h>
 #include <stdlib.h>
+#include <limits.h>
 
 
 int
 do_test (void)
 {
   /* XXX This test might require architecture and system specific changes.
      There is no guarantee that this signal number is invalid.  */
-  int e = pthread_kill (pthread_self (), SIGRTMAX + 10);
+  int e = pthread_kill (pthread_self (), INT_MAX);
   if (e == 0)
     {
       puts ("kill didn't failed");